This is the mail archive of the
mailing list for the GCC project.
Re: Moving to git
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Jeff Law <law at redhat dot com>
- Cc: Jason Merrill <jason at redhat dot com>, "gcc\ at gnu dot org" <gcc at gnu dot org>
- Date: Thu, 20 Aug 2015 22:26:01 +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>
* Jeff Law:
> I suspect Jakub will strongly want to see some kind commit hook to
> associate something similar to an SVN id to each git commit to support
> his workflow where the SVN ids are associated with the compiler
> binaries he keeps around for very fast bisection.
As long as we do not rebase,
git log --pretty=format: | wc -l
is actually pretty close to a revision number, and it's reasonably
quick to compute. The number will be meaningful only within a single
branch. It's also prudent to capture the head commit hash when the
number is generated because subsequent merges may make it complicated
to map the number back to the original branch head when the number was
> ISTM that within that namespace, folks ought to have the freedom to
> use whatever works for them. If folks want to create a transient
> branch, push-rebase-push on that branch, then later remove it, I tend
> to think, why not let them.
They could use a completely separate repository, too, and still have
working merges from mainline.