On Wed, Jan 28, 2009 at 11:26 AM, Poor Yorick <org.gnu.bug-coreut...@pooryorick.com> wrote:
> Couldn't check out coreutils at work because corporate firewall blocked > everything but http access, which always hung during git-clone. Perhaps if you try a shallow clone by using "git clone --depth 2" or similar, this may work around the problem. Or not, it depends on what causes the hang. > Finally got > a copy of the repository at home, but no mention of 6.12-213-gcfe3602 in > logs or tags. This is a very good question. SImply put, 6.12-213-gcfe3602 is whatever version of coreutils causes ./build-aux/git-version-gen to print that string. So here I have $ ./build-aux/git-version-gen .version ; echo 6.12.7-86535-dirty If I want 6.12-213-gcfe3602 then I need to somehow know that the final part of the string "6.12-213-gcfe3602" is an abbreviated version number. I don't know where a person should ideally go to figure this out, if they don't know that build-aux/git-version-gen exists. One answer is that the configure.ac file normally contains the package version number, and in the case of coreutils, this says: # Make inter-release version strings look like, e.g., v6.9-219-g58ddd, which # indicates that it is built from the 219th delta (in _some_ repository) # following the v6.9 tag, and that 58ddd is a prefix of the commit SHA1. AC_INIT([GNU coreutils], m4_esyscmd([build-aux/git-version-gen .tarball-version]), [bug-coreut...@gnu.org]) $ git checkout gcfe3602 error: pathspec 'gcfe3602' did not match any file(s) known to git. Of course. "g" isn't a hex digit, I cut-and-pasted too much. Try again without it.. $ git checkout cfe3602 HEAD is now at cfe3602... seq: solve e13188e7ef7bbd609c1586332a335b4194b881aa more cleanly Aha, that seems satisfactory. Of course if you specify too small a value for --depth in your clone command, the revision you are looking for may not be in your local repository - you can deepen your local repository with "git fetch --depth". > Basically, my goal is to find the most bug-fixed version of the 6.12 series. > Perhaps what I really want is the v6.12 tag in git (git newbie here)? But > I'm curious how these various snapshots can be identified and found. Help? I hope this helped a bit. Thanks, James. _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils