This is the mail archive of the
mailing list for the GCC project.
Re: Proposal for the transition timetable for the move to GIT
- From: Iain Sandoe <iain at sandoe dot co dot uk>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>, Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>, "Eric S. Raymond" <esr at thyrsus dot com>, GCC Development <gcc at gcc dot gnu dot org>, Alexandre Oliva <oliva at gnu dot org>, Jeff Law <law at redhat dot com>, Mark Wielaard <mark at klomp dot org>, Jakub Jelinek <jakub at redhat dot com>, Segher Boessenkool <segher at kernel dot crashing dot org>, Richard Biener <richard dot guenther at gmail dot com>
- Date: Fri, 10 Jan 2020 12:08:45 +0000
- Subject: Re: Proposal for the transition timetable for the move to GIT
- References: <5DCEA32B-3E36-4400-B931-9F4E2A8F3FA5@linaro.org> <155B5BFD-6ECF-4EBF-A38C-D6DD178FB497@linaro.org> <firstname.lastname@example.org> <9B71A0F7-CD93-4636-BFC7-1D1DBC040F07@linaro.org> <email@example.com> <6EE7BD53-6677-49D2-BCDD-56CD7DA855E9@linaro.org> <firstname.lastname@example.org> <88B4DAF3-33C1-445F-8F5A-809D5463D0F9@linaro.org> <20200108221119.GA94728@thyrsus.com> <alpine.DEB.email@example.com> <20200109023804.GR3191@gate.crashing.org> <27A7DEAB-42B9-4A5A-BE89-618F7ED2347E@linaro.org> <firstname.lastname@example.org> <CAFiYyc1PGyG4g5LHwdNmjY7Jp5DVvanOh8YGifjGP1z5xzKbxQ@mail.gmail.com>
Richard Biener <email@example.com> wrote:
On Fri, Jan 10, 2020 at 10:49 AM Richard Earnshaw (lists)
On 10/01/2020 07:33, Maxim Kuvyrkov wrote:
On Jan 9, 2020, at 5:38 AM, Segher Boessenkool
On Wed, Jan 08, 2020 at 11:34:32PM +0000, Joseph Myers wrote:
As noted on overseers, once Saturday's DATESTAMP update has run at
UTC on Saturday, I intend to add a README.MOVED_TO_GIT file on SVN
and change the SVN hooks to make SVN readonly, then disable gccadmin's
cron jobs that build snapshots and update online documentation until
are ready to run with the git repository. Once the existing git mirror
has picked up the last changes I'll make that read-only and disable
cron job as well, and start the conversion process with a view to
the converted repository in place this weekend (it could either be made
writable as soon as I think it's ready, or left read-only until people
have had time to do any final checks on Monday). Before then, I'll
on hooks, documentation and maintainer-scripts updates.
Where and when and by who was it decided to use this conversion?
Joseph, please point to message on gcc@ mailing list that expresses
consensus of GCC community to use reposurgeon conversion. Otherwise,
it is not appropriate to substitute one's opinion for community
I've gone back through this thread (if I've missed, or misrepresented,
anybody who's expressed an opinion I apologize now).
Segher Boessenkool <firstname.lastname@example.org>
"If Joseph and Richard agree a candidate is good, then I will agree as
well. All that can be left is nit-picking, and that is not worth it
Jeff Law <email@example.com>
"When Richard and I spoke we generally agreed that we felt a reposurgeon
conversion, if it could be made to work was the preferred solution,
followed by Maxim's approach and lastly the existing git-svn mirror."
Richard Earnshaw (lists) <Richard.Earnshaw@arm.com>
FWIW, I now support using reposurgeon for the final conversion.
And, of course, I'm taking Joseph's opinion as read :-)
So I don't see any clear dissent and most folks just want to get this
Just to chime in I also just want to get it done (well, I can handle
SVN as well :P).
I trust Joseph, too, but then from my POV anything not worse than the
mirror works for me. Thanks to Maxim anyway for all the work - without
we'd not switch in 10 other years...
Btw, "consensus" among the quiet doesn't usually work and "consensus" among
the most vocal isn't really "consensus". I think GCC (and FOSS) works by
giving power to those who actually do the work. Doesn't make it easier
there are two, of course ;)
Thanks to all those who’ve put (a lot of) effort into doing this work and
challenged and tested the conversions, for my part, I am also happy to take
One minor nit (and accepted that this might be too late).
mail commit messages like this:
[gcc-reposurgeon-8(refs/users/jsm28/heads/test-branch)] Test git hooks
interaction with Bugzilla.
seem to have a title stretched by redundant infomation ;
at least "users/jsm28/test-branch” would seem to contain all the necessary
will commits in the user namespace appear on the mailing list in the end?