This is the mail archive of the
mailing list for the binutils project.
Re: A Proposal to Move to Git
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Steve Ellcey <sellcey at mips dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, GDB Development <gdb at sourceware dot org>, Binutils Development <binutils at sourceware dot org>
- Date: Thu, 22 Aug 2013 15:16:18 +0100
- Subject: Re: A Proposal to Move to Git
- References: <8738q4gj7a dot fsf at fleche dot redhat dot com> <1377099478 dot 5770 dot 76 dot camel at ubuntu-sellcey>
On 21/08/13 16:37, Steve Ellcey wrote:
> On Tue, 2013-08-20 at 15:12 -0600, Tom Tromey wrote:
>> I'd like to do the final switch around mid-September. Not sooner,
>> because I am going to be away for a little while near the end of
>> August, and I want to be available to fix problems.
> There was a comment on the gdb list about releasing GDB 7.7 before the
> transition, I wonder if it would make sense to release a Binutils 2.24
> as well? In general, I am in favor of the transition and I don't think
> doing (or not doing) a binutils 2.24 release should be a blocker for the
> move to git, but I wouldn't mind seeing a new release before the
If you switch after the releases have been made you also need to
consider how you'll handle 'dot' releases should they be necessary. Are
they going to come from the CVS source base and then be re-imported into
GIT? Or, are you going to use a different process to handle them from
that used to produce the main release?