Re: I just pulled and built 'next'...

> Uwe Kleine-König <zeisberg@informatik.uni-freiburg.de> wrote:
> > Shawn O. Pearce wrote:
> > >   $ git rev-list v1.5.0-rc0..next | wc -l
> > >   687
> > >   $ git rev-list v1.4.4.4..next | wc -l
> > >   1051
> > > 
> > > So what about doing Junio's suggestion of going by topology and
> > > coming up with the possible set of tags (v1.5.0-rc0 and v1.4.4.4
> > > right now), and if more than one is found compute the number of
> > > commits between each tag and the requested revision, and take the
> > > tag that has a smallest number of commits?
> >
> > One scenario where this will fail is when a bugfix is commited on top of
> > v1.4.4.4 and then is merged into v1.5.0-rc0+gabcdef.
> 
> Actually it still works, and does what you want.  The scenario you
> are describing is exactly the one that caused this bug to appear,
> and is the one my suggestion is trying to offer a partly sane
> solution to.