Okay, that must have been a misunderstanding. I don't know what DAG is. Do I still need to worry that with default options, under any realistic circumstances the command may not find the most recent tag?
Am Dienstag, 8. Dezember 2015 21:51:31 UTC+1 schrieb Philip Oakley: > > I may have mis-read the question… > > > > If the question is to say that the ’10 candidates’ is too few because you > think that it is ‘COMMIT candidates’, then that would be a misreading of > the man page. > > > > It is the number of candidate TAGS that is being limited for the DAG > graph’s depth comparison. The depth value can be as large as you like (i.e. > as large as is needed given the history graph), as long as there is a tag > to act as the base for the description. > > > > The other thing is to also add the “--always" option so that even if there > isn’t a suitable tag you still at least get an answer (with the minimal > sha1 of the commit (rev/branch) being described. > > > > Philip > > > > *From:* > ... -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.