From: Jeff Law <law@redhat.com>
To: Ramana Radhakrishnan <ramana.gcc@googlemail.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: Richard Guenther <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git
Date: Thu, 16 May 2019 19:07:00 -0000 [thread overview]
Message-ID: <e79c95db-6352-5afd-be1e-63ec6b1cbd5f@redhat.com> (raw)
In-Reply-To: <CAJA7tRZ3KgPsLJ9o06hD+urhjD4rgawe2yoEXzzRdYLSksvxyA@mail.gmail.com>
On 5/16/19 12:36 PM, Ramana Radhakrishnan wrote:
> On Thu, May 16, 2019 at 5:41 PM Maxim Kuvyrkov
> <maxim.kuvyrkov@linaro.org> wrote:
>>
>>> On May 16, 2019, at 7:22 PM, Jeff Law <law@redhat.com> wrote:
>>>
>>> On 5/15/19 5:19 AM, Richard Biener wrote:
>>>>
>>>> For the official converted repo do we really want all (old)
>>>> development branches to be in the
>>>> main git repo? I suppose we could create a readonly git from the
>>>> state of the whole repository
>>>> at the point of conversion (and also keep the SVN in readonly mode),
>>>> just to make migration
>>>> of content we want easy in the future?
>>> I've always assumed we'd keep the old SVN tree read-only for historical
>>> purposes. I strongly suspect that, ignoring release branches, that
>>> non-active branches just aren't terribly interesting.
>>
>> Let's avoid mixing the two discussions: (1) converting svn repo to git (and getting community consensus to switch to git) and (2) deciding on which branches to keep in the new repo.
>>
>
> I'm hoping that there is still community consensus to switch to git.
>
> Personally speaking, a +1 to switch to git.
Absolutely +1 for converting as well.
jeff
next prev parent reply other threads:[~2019-05-16 19:07 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 16:11 Maxim Kuvyrkov
2019-05-14 21:20 ` Segher Boessenkool
2019-05-15 8:34 ` Maxim Kuvyrkov
2019-05-15 18:47 ` Segher Boessenkool
2019-05-16 9:44 ` Maxim Kuvyrkov
2019-05-15 11:19 ` Richard Biener
2019-05-15 12:08 ` Maxim Kuvyrkov
2019-05-15 18:42 ` Eric Gallager
2019-05-16 0:33 ` Paul Koning
2019-05-16 9:53 ` Maxim Kuvyrkov
2019-05-16 16:22 ` Jeff Law
2019-05-16 16:40 ` Maxim Kuvyrkov
2019-05-16 18:36 ` Ramana Radhakrishnan
2019-05-16 19:07 ` Jeff Law [this message]
2019-05-16 22:04 ` Jonathan Wakely
2019-05-17 11:33 ` Martin Liška
2019-05-16 23:54 ` Joseph Myers
2019-05-17 8:19 ` Richard Sandiford
2019-05-17 19:51 ` Segher Boessenkool
2019-05-17 20:59 ` Steve Ellcey
2019-05-17 21:23 ` Jason Merrill
2019-05-20 22:42 ` Joseph Myers
2019-05-21 14:24 ` Richard Earnshaw (lists)
2019-05-21 14:45 ` Jeff Law
2019-05-21 15:02 ` Richard Earnshaw (lists)
2019-05-21 16:44 ` Segher Boessenkool
2019-05-23 22:33 ` Joseph Myers
2019-05-24 8:58 ` Segher Boessenkool
2019-05-24 12:02 ` Florian Weimer
2019-05-29 1:50 ` Joseph Myers
2019-05-29 13:04 ` Segher Boessenkool
2019-05-31 0:16 ` Joseph Myers
2019-06-02 23:13 ` Segher Boessenkool
2019-06-03 22:33 ` Joseph Myers
2019-06-03 22:49 ` Segher Boessenkool
2019-06-05 18:04 ` Jason Merrill
2019-06-06 10:14 ` Richard Earnshaw (lists)
2019-06-06 23:41 ` Joseph Myers
2019-06-06 23:50 ` Ian Lance Taylor
2019-06-07 9:32 ` Richard Earnshaw (lists)
2019-06-06 23:36 ` Joseph Myers
2019-07-22 9:05 ` Maxim Kuvyrkov
2019-05-16 23:06 ` Joseph Myers
2019-05-17 12:22 ` Martin Liška
2019-05-17 12:39 ` Jakub Jelinek
2019-05-19 7:35 ` Martin Liška
2019-05-19 8:11 ` Segher Boessenkool
2019-05-19 19:21 ` Marek Polacek
2019-05-19 19:46 ` Andreas Schwab
2019-05-19 19:54 ` Segher Boessenkool
2019-05-19 20:01 ` Andrew Pinski
2019-05-19 20:06 ` Marek Polacek
2019-05-20 7:29 ` Martin Liška
2019-05-20 13:56 ` Florian Weimer
2019-05-20 14:18 ` Segher Boessenkool
2019-05-20 14:25 ` Jakub Jelinek
2019-05-20 14:26 ` Andreas Schwab
2019-05-20 14:29 ` Jakub Jelinek
2019-05-20 14:36 ` Andreas Schwab
2019-05-20 15:04 ` Segher Boessenkool
2019-05-17 14:59 ` Maxim Kuvyrkov
2019-05-19 7:09 ` Martin Liška
2019-05-17 14:56 ` Maxim Kuvyrkov
2019-05-17 13:07 ` Jason Merrill
2019-05-17 15:08 ` Maxim Kuvyrkov
2019-05-20 22:48 ` Joseph Myers
2019-05-28 10:44 ` Maxim Kuvyrkov
2019-07-16 10:21 ` Maxim Kuvyrkov
2019-07-16 12:40 ` Jason Merrill
2019-07-16 14:27 ` Maxim Kuvyrkov
2019-07-20 11:24 ` Maxim Kuvyrkov
2019-07-22 9:35 ` Maxim Kuvyrkov
2019-08-01 20:43 ` Jason Merrill
2019-08-02 8:41 ` Maxim Kuvyrkov
2019-08-02 8:57 ` Richard Biener
2019-08-02 10:27 ` Martin Liška
2019-08-02 10:54 ` Maxim Kuvyrkov
2019-08-02 11:01 ` Martin Liška
2019-08-02 11:06 ` Richard Biener
2019-08-02 11:35 ` Martin Liška
2019-08-02 22:31 ` Jason Merrill
2019-08-05 13:20 ` Martin Liška
2019-08-05 15:20 ` Monotonically increasing counter (was Re: [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git) Jason Merrill
2019-08-05 15:34 ` Jakub Jelinek
2019-08-05 15:45 ` Richard Earnshaw (lists)
2019-08-05 18:22 ` Jason Merrill
2019-08-14 18:49 ` Jason Merrill
2019-09-19 19:29 ` Jason Merrill
2019-09-21 18:18 ` Segher Boessenkool
2019-09-21 20:31 ` Nicholas Krause
2019-09-21 21:32 ` Jason Merrill
2019-09-22 0:20 ` Segher Boessenkool
2019-08-02 14:35 ` [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git Segher Boessenkool
2019-08-02 14:55 ` Maxim Kuvyrkov
2019-08-05 16:43 ` Mike Stump
2019-08-05 8:24 ` Maxim Kuvyrkov
2019-08-06 11:16 ` Maxim Kuvyrkov
2019-08-23 8:27 ` Maxim Kuvyrkov
2019-08-23 22:08 ` Joseph Myers
2019-09-13 7:20 ` Maxim Kuvyrkov
2019-08-02 8:35 ` Maxim Kuvyrkov
2019-08-02 14:14 ` Maxim Kuvyrkov
2019-08-02 15:47 ` Segher Boessenkool
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=e79c95db-6352-5afd-be1e-63ec6b1cbd5f@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=maxim.kuvyrkov@linaro.org \
--cc=pbonzini@redhat.com \
--cc=ramana.gcc@googlemail.com \
--cc=richard.guenther@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).