Solved where is official online source code (for freeBSD kernel / tree)

debguy

debguy

http://svnweb.freebsd.org

https://github.com/freebsd/freebsd

i've heard two stories: freebsd preferrs cvs and github will rule. is someone trying to "push" github (and whoever registered the freebsd git source) as the "official maintainers"?

------------------------
WHY: i'm familiar with linux CHANGELOG but not freeBSD kernel changelog. i'd like to compare the two. to do that i need to find the (changelog or the freeBSD equivalent) for kernel source code patches.

Any comments on "how stable" changes are to either kernel are also welcome. (ex, i know in linux bugs are frequent (rather, lack of knowlege + bugs), and that many fixes are reverted and refixed. is freeBSD any different in that respect? that's what i'm looking for). are some of the "changelog signers" working on both kernels?

any other comments on freeBSD v. linux kernel are welcome. i'm mostly interested in "what goes wrong" with signed changes and who's signing them.
 
The SVN repo is the official repo where all the work happens. The GitHub repo is just a mirror of the former, maintained by folks who personally prefer Git over SVN. The GitHub repo is usually pretty up-to-date, but all FreeBSD releases and official patches are built and distributed from the SVN repo. Whether there's any kind of shim between the two that allows active contributors who use Git to submit patches to the official SVN tree, I don't know.

CVS was previously used to maintain the source code, but was replaced with SVN years ago.
 
i mean to say svn. i haven't found a whole kernel changelog. unsure if there is one - i see only logs on a per file basis. i guess i can somehow use svn to pull and cat all logs if i get the time to.
 
I don't think it's possible to find a changelog for just the kernel. It's easy enough to do this with Linux, since it's developed on its own in a single place. But the FreeBSD kernel is not a discrete software package. FreeBSD development is holistic, and it's often not possible to make changes to components that don't touch upon other components. Fixes and updates that require changes to the kernel often require changes to other system components, or vice versa, and those changes are made in the same place at the same time.
 
Another important issue is that Github (at least the repository you're mentioning) is hosting CURRENT which is the developer snapshot; a version not meant for production use.

A solid way to get hold of the source code is to use # svnlite co https://svn.freebsd.org/base/releng/11.1 /usr/src (or 11.2 of course). If you then take a closer look at /usr/src/UPDATING you'll find a changelog which describes all recent changes to the sourcetree.

Of course svnlite log will help too, somewhat.
 
ShelLuser said:
Another important issue is that Github (at least the repository you're mentioning) is hosting CURRENT which is the developer snapshot; a version not meant for production use.
Click to expand...
No, the GitHub repository contains all branches. The more or less equivalent to your svn command would be something like: git clone -b releng/11.1 --single-branch https://github.com/freebsd/freebsd /usr/src
 
You must log in or register to reply here.
Back
Top