On Friday 20 January 2012 23:50:23 Sitaram Chamarty wrote: > On Fri, Jan 20, 2012 at 7:03 PM, Brian Foster <brian.foster@xxxxxxxxxxxx> wrote: >[ ... ] > > x---Y---y---y---y HEAD > > / > > ...--o---o---C---o---S > > \ > > n---n---N---*---* other > > > > In a script, how can I determine commit Y is reachable > > from the current HEAD ? [ ... ] > > I've been using 'git rev-list HEAD..Y'. If it produces any output, > Y is not reachable from HEAD (there is something in Y that is not > in HEAD). What's interesting about this solution, at least with GIT v1.7.6.1 (I haven't tried other versions), is ‘git rev-list HEAD..Y’ does seem to work (if there is any output, then Y is not reachable from HEAD), but ‘git rev-list --quiet HEAD..Y’ does _not_ work (it seems to always(?) exit status 0). I am probably misunderstanding ‘--quiet’, which the man page cryptically describes as “... allow the caller to test the exit status to see if a range of objects is fully connected (or not).” What is meant here by “fully connected” ? cheers! -blf- -- Brian Foster Principal MTS, Software | La Ciotat, France Maxim Integrated Products | Web: http://www.maxim-ic.com/ -- 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