From: Fred Cooke <fred.cooke@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Richard Earnshaw <rearnsha@arm.com>,
Steve Ellcey <sellcey@mips.com>, Tom Tromey <tromey@redhat.com>,
GDB Development <gdb@sourceware.org>,
Binutils Development <binutils@sourceware.org>
Subject: Re: A Proposal to Move to Git
Date: Thu, 22 Aug 2013 14:39:00 -0000 [thread overview]
Message-ID: <CABZhLO9ZG2LvTrFoonpJ33oS3EJ0JXrT6=TH2eCnXa-0OCNdYg@mail.gmail.com> (raw)
In-Reply-To: <20130822142513.GH5147@adacore.com>
Using two systems in parallel seems to be a terrible idea. One nice
thing with Git is that the release branch, once imported, could be
practiced on locally for honing the new process.
On Thu, Aug 22, 2013 at 4:25 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> 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?
>
> It's a good point. I thought we'd keep using CVS for 7.7.x while
> transitioning to git for "HEAD". On the other hand, I like Tristan's
> confidence, so I'd be OK with switching to git before we create
> the 7.7 branch. Also, why force ourselves to use two systems, one
> of them being phased out, when we can use just one?
>
> --
> Joel
next prev parent reply other threads:[~2013-08-22 14:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 21:12 Tom Tromey
2013-08-20 21:16 ` Andrew Pinski
2013-08-20 21:26 ` Joseph S. Myers
2013-08-20 21:19 ` Joel Brobecker
2013-08-20 21:21 ` Paul_Koning
2013-08-20 22:59 ` Phil Muldoon
2013-08-21 15:05 ` Eli Zaretskii
2013-08-21 15:32 ` Andreas Schwab
2013-08-21 15:54 ` Eli Zaretskii
2013-08-26 8:05 ` Andreas Schwab
2013-08-21 18:40 ` Steinar Bang
2013-08-21 20:05 ` Eli Zaretskii
2013-08-21 20:38 ` Andreas Schwab
2013-08-22 18:56 ` Florian Weimer
2013-08-21 15:38 ` Steve Ellcey
2013-08-21 15:50 ` Joel Brobecker
2013-08-22 6:10 ` Tristan Gingold
2013-08-22 14:16 ` Richard Earnshaw
2013-08-22 14:25 ` Joel Brobecker
2013-08-22 14:39 ` Fred Cooke [this message]
2013-08-22 20:10 ` Mark Kettenis
2013-08-22 20:21 ` Fred Cooke
2013-08-22 20:22 ` David Miller
2013-08-22 20:48 ` Andrew Pinski
2013-08-22 21:07 ` Andreas Schwab
2013-08-22 21:10 ` Tom Tromey
2013-08-23 15:40 ` H.J. Lu
2013-08-23 15:55 ` Joel Brobecker
2013-08-23 16:03 ` Paul_Koning
2013-08-23 16:05 ` H.J. Lu
2013-08-26 12:37 ` NightStrike
[not found] ` <upzc38pvcv1w.fsf@dod.no>
2013-08-27 16:21 ` asmwarrior
2013-08-23 16:03 ` H.J. Lu
2013-08-23 16:09 ` Joel Brobecker
2013-08-23 16:24 ` Matt Rice
2013-08-23 16:37 ` H.J. Lu
2013-08-23 16:47 ` Matt Rice
2013-08-23 17:01 ` H.J. Lu
[not found] ` <87siy070su.fsf@dod.no>
2013-08-24 0:27 ` Doug Evans
2013-08-22 23:55 ` Alan Modra
2013-08-30 22:58 ` Hans-Peter Nilsson
2013-08-30 23:37 ` Joseph S. Myers
2013-08-31 2:05 ` Hans-Peter Nilsson
2013-08-31 16:58 ` Joseph S. Myers
2013-09-04 16:55 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABZhLO9ZG2LvTrFoonpJ33oS3EJ0JXrT6=TH2eCnXa-0OCNdYg@mail.gmail.com' \
--to=fred.cooke@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=rearnsha@arm.com \
--cc=sellcey@mips.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox