[Cc: git@xxxxxxxxxxxxxxx] Junio C Hamano wrote: > Han-Wen Nienhuys <hanwen@xxxxxxxxx> writes: > >> Jakub Narebski escreveu: >>> >>> _Which_ INIT? In git there can be more than one root commit. In git.git >> >> I don't really care, but I would like git-describe to produce something >> useful in the absence of tags. The -g<SHA-1> already makes the commit >> uniquely identifiable. > > Then you would script like this: > > #!/bin/sh > git describe "$1" 2>/dev/null || git rev-parse --verify "$1" > > I do not think it a good idea to make "git-describe" itself do > the above, as the user of describe may want to fall back on > something other than "rev-parse --verify" after ||. By the way, new git-describe gives us also number of commits since tag, and it would be nice to have number of commits since init... but that can be easily obtained using "git rev-list $1 | wc -l". I guess that some use git-describe with --abbrev=0 to get closest preceding tag: getting INIT would confuse them. That said, we could use e.g. INITg2a45ba+10-g4ee2ab -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html