This is the mail archive of the
mailing list for the GCC project.
Re: Moving to git
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Jason Merrill <jason at redhat dot com>, Jeff Law <law at redhat dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 24 Aug 2015 19:08:31 +0200
- Subject: Re: Moving to git
- Authentication-results: sourceware.org; auth=none
- References: <55D61512 dot 8010002 at redhat dot com> <55D61B23 dot 3000309 at redhat dot com> <55D63403 dot 4000603 at redhat dot com> <20150824081741 dot GB9425 at tucnak dot redhat dot com> <mvmwpwl85a9 dot fsf at hawking dot suse dot de>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Mon, Aug 24, 2015 at 10:22:22AM +0200, Andreas Schwab wrote:
> Jakub Jelinek <firstname.lastname@example.org> writes:
> > And for those really identifying them by sha1 hashes is significantly
> > worse than using monotonically increasing small number, sha1 hashes
> > are impossible to remember, and you don't know what is earlier and
> > what is later from just looking at it.
> git describe gives you such a number (relative to a tag).
But it is not unique across different branches, and furthermore, what is the
fast way to go from the number to a commit? If you have to git describe
all the commits to find the one you are looking for, then it is not what I