[PATCH] Clean up references to Subversion in documentation sources.
Segher Boessenkool
segher@kernel.crashing.org
Tue Jan 28 13:28:00 GMT 2020
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
More information about the Libstdc++
mailing list