This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Clean up references to Subversion in documentation sources.

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.

I'm as old-school as any of you guys, so take me seriously when I say
these are not popular for merely faddish reasns. The integration of
repository management, issue tracking, and continuous integration they
offer really does offer a major step up in productivity and
auditability.

I *will* be nudging the GCC project community to think about this.
-- 
		<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]