This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: onwards to git
- From: Jim Meyering <jim at meyering dot net>
- To: Roland McGrath <roland at redhat dot com>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, libc-ports at sourceware dot org
- Date: Fri, 01 May 2009 08:29:28 +0200
- Subject: Re: onwards to git
- References: <49F89C2D.5060702@redhat.com> <Pine.LNX.4.64.0904292008041.31467@digraph.polyomino.org.uk> <20090429203933.08694FC3BF@magilla.sf.frob.com> <Pine.LNX.4.64.0904292110320.31467@digraph.polyomino.org.uk> <87zldy9nj0.fsf@meyering.net> <20090430194732.49B64FC3BF@magilla.sf.frob.com> <873abpao4n.fsf@meyering.net> <20090430203854.7A206FC3BF@magilla.sf.frob.com> <87fxfp94zw.fsf@meyering.net> <20090430221928.9CA9FFC3BF@magilla.sf.frob.com>
Roland McGrath wrote:
>> Ok. I'll plan to switch glibc-ports on Monday or Tuesday,
>> along with testing/installing at least the commit-email hook.
>
> I'm not clear on what you mean by "switch glibc-ports" here.
> The only step we need done now is to make git commit emails work.
I meant "switch it to git" by "prohibiting cvs commits, etc." i.e.,
follow the 4 steps I described.
If you want something else, please be excruciatingly precise.
I.e., at least one person objected to cvs-removing all files.
>> I haven't looked at the bugzilla one at all yet.
>
> That one might be more different than it was before.
> IIRC we got that script from the gcc bugzilla masters.
> (But if so that must have been before gcc went to svn.)
>
> Also, we have not discussed git commit log entry conventions yet.
> When we figure that all out, it might be that commit logs rather
> than ChangeLog* file diffs are what gets massaged for bugzilla.
> More or less, we can start over from scratch to address the desire
> for automagic bugzilla comments from commits, rather than worrying
> about converting the existing scripts to do exactly the same thing
> with a different SCM.
Good!