This is the mail archive of the
mailing list for the GCC project.
Re: Moving to git
- From: Martin Jambor <mjambor at suse dot cz>
- To: gcc at gcc dot gnu dot org
- Date: Fri, 21 Aug 2015 11:06:15 +0200
- Subject: Re: Moving to git
- Authentication-results: sourceware.org; auth=none
- References: <55D61512 dot 8010002 at redhat dot com> <1440099112 dot 18943 dot 38 dot camel at surprise>
On Thu, Aug 20, 2015 at 03:31:52PM -0400, David Malcolm wrote:
> On Thu, 2015-08-20 at 13:57 -0400, Jason Merrill wrote:
> > I hear that at Cauldron people were generally supportive of switching
> > over to git as the primary GCC repository, and talked about me being
> > involved in that transition. Does anyone have more information about
> > this discussion?
> > Our current workflow translates over to a git master pretty easily:
> > basically, in the current git-svn workflow, replace git svn rebase and
> > git svn dcommit with git pull --rebase and git push.
> > It should be pretty straightforward to use the existing git mirror as
> > the master repository; the main adjustment I'd want to make is rewriting
> > the various subdirectory branches to be properly represented in git.
> > This is straightforward, but we'll want to stop SVN commits to
> > subdirectory branches shortly before the changeover.
> > It would be good to have a more explicit policy on branch/tag creation,
> > rebasing, and deletion in the git world where branches are lighter
> > weight and so more transient.
> If we're going to migrate to git (I hope so), can we also please
> *slightly* revise the policy on commit messages, to add meaningful
> titles to commits?
I second this, looking at history with git shortlog or in tig
(something I do every now and then) would then be much more
And yes, we can actually start doing that now and people using git
mirror would benefit immediately.
Thanks for bringing this up,