From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Sandra Loosemore <sandra@codesourcery.com>,
gcc-patches@gcc.gnu.org, libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] Clean up references to Subversion in documentation sources.
Date: Mon, 27 Jan 2020 20:11:00 -0000 [thread overview]
Message-ID: <20200127193302.GB22482@gate.crashing.org> (raw)
In-Reply-To: <20200113181215.GA126826@thyrsus.com>
On Mon, Jan 13, 2020 at 01:12:15PM -0500, Eric S. Raymond wrote:
> Jonathan Wakely <jwakely@redhat.com>:
> > Email the patches to gcc-patches@gcc.gnu.org, that's how things get
> > merged.
> >
> > We're not looking to change any workflows now.
>
> Roger that.
>
> Once the dust from the conversion has settled, though, there is a
> related issue I intend to bring up on the main list.
>
> You've only collected about 60% of the potential benefits from git
> by adopting git itself. The other 40% would come from moving
> to to one of the modern git-centric forges like GitHub or GitLab.
NAK.
Our development model fits our needs well, even with all its warts.
A "pull request" model would not fit well *at all*.
The "everything passes through email" model is *good*, not in the least
because it puts everyone on a level playing field. Everyone can see
everything, and comment on everything.
And if it slows you down, well, that is a good thing as well probably!
Thought and carefulness and looking at things from multiple angles is
what we need, not raw speed: we need good changes, we do not need making
it easier to get your changes included at the cost of basic quality.
Anyway, 90% of the advantages of using Git come from using it *locally*,
which many of us have been doing since forever and a day already.
Segher
next prev parent reply other threads:[~2020-01-27 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 16:09 Eric S. Raymond
2020-01-13 16:21 ` Sandra Loosemore
2020-01-13 16:40 ` Joseph Myers
2020-01-13 17:35 ` Eric S. Raymond
2020-01-13 18:06 ` Jonathan Wakely
2020-01-13 18:38 ` Eric S. Raymond
2020-01-27 20:11 ` Segher Boessenkool [this message]
2020-01-20 4:40 ` Sandra Loosemore
2020-01-20 23:05 ` Jonathan Wakely
2020-01-13 17:12 ` Jonathan Wakely
2020-01-13 17:27 ` Jonathan Wakely
2020-01-14 11:46 ` Gerald Pfeifer
2020-01-15 21:52 ` Jonathan Wakely
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=20200127193302.GB22482@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=esr@thyrsus.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=sandra@codesourcery.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).