On Wed, September 21, 2005 2:28 pm, Bill Davidsen said:
> But that pulls the current tree, doesn't it? Not the git release?
It pulls the latest git release plus any extra commits that have been made
since, if any. Now, if you have a specific reason to test a -gitX
release you can simply lookup which commit corresponds to the -gitX
release and check it out of the git repository and build it. Actually, I
just posted a script that lets you check out a build by -gitX name instead
of having to manually lookup the corresponding commit id.
> For purposes of bug reporting and fixing, I would think that having some
> reproducible version is superior. If I say git3, anyone can get it, it
> would appear that "git pull" isn't as deterministic.
There are cases where using the -gitX release helps a bit. But there's
nothing magic about a -gitX release, it's just a collection of whatever
commits existed when the timed build procedure ran.
Using git you get the choice of using -gitX builds or tracking directly
from the most recent commit as the situation demands. Therefore if Linus
commits a fix beyond the latest -gitX release you happen to need, you're
good to go. If you want to track the latest -gitX release, you can do
that with git too.
Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |