On Mai 19 2019, Marek Polacek <pola...@redhat.com> wrote: > On Sun, May 19, 2019 at 03:11:08AM -0500, Segher Boessenkool wrote: >> On Sun, May 19, 2019 at 09:35:45AM +0200, Martin Liška wrote: >> > Do we really need a commit integer numbers after the transition? I know >> > we're used to it. >> > But git commit hash provides that same. >> >> Revision numbers are nice short text strings, and from a revision number >> you can see approximately when it happened, and from two revision numbers >> on the same branch you can trivially tell which one is older. Those are >> nice features. But we can live without it, IMO. > > Since I do many bisections a day, losing this capability would be Very Bad. > Without it, there's no range, and without a range, there's nothing to > _bisect_.
What's wrong with git bisect? It does everything you need. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
