This is the mail archive of the
mailing list for the GCC project.
Re: Moving to git
- From: Ramana Radhakrishnan <ramana dot gcc at googlemail dot com>
- To: Andreas Schwab <schwab at linux-m68k dot org>
- Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, Jason Merrill <jason at redhat dot com>, Jeff Law <law at redhat dot com>, "gcc at gnu dot org" <gcc at gnu dot org>, Jakub Jelinek <jakub at redhat dot com>
- Date: Fri, 21 Aug 2015 15:39:12 +0100
- Subject: Re: Moving to git
- Authentication-results: sourceware.org; auth=none
- References: <55D61512 dot 8010002 at redhat dot com> <55D61B23 dot 3000309 at redhat dot com> <55D63403 dot 4000603 at redhat dot com> <CAJA7tRahuaA36w76YD0nE+6ur1Y8T1ThZ8ssSmGgRmzT9bUcBA at mail dot gmail dot com> <CAH6eHdTcMMgHBax=x42aAE+LdRyKnzNhaLxvc_VcPQVP_P7nog at mail dot gmail dot com> <CAJA7tRYwEMxTrFmFNYg0Mh9QTLyNOtVPH7kjjSTzS82RPyXHfQ at mail dot gmail dot com> <87zj1kwx6g dot fsf at igel dot home>
- Reply-to: ramrad01 at arm dot com
On Fri, Aug 21, 2015 at 3:09 PM, Andreas Schwab <email@example.com> wrote:
> Ramana Radhakrishnan <firstname.lastname@example.org> writes:
>> On Fri, Aug 21, 2015 at 11:48 AM, Jonathan Wakely <email@example.com> wrote:
>>> Teams following a different model could use a separate repo shared by
>>> those developers, not the gcc.gnu.org one. It's much easier to do that
>>> with git.
>> Yes you are right they sure can, but one of the reasons that teams are
>> doing their development on a feature branch is so that they can obtain
>> feedback and collaborate with others in the community.
> It is also much easier for others to pull from foreign repositories with
> git, so this isn't a severe downside.
It isn't a severe downside as long as people aren't prevented from
discussing / recording such patches on gcc-patches because said
branches are hosted in a "foreign repository".
> Andreas Schwab, firstname.lastname@example.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."