Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: Ian Lance Taylor <iant@google.com>,
	Peter Bergner <bergner@vnet.ibm.com>,
	Tom Tromey <tromey@redhat.com>,
	GDB Development <gdb@sourceware.org>,
	Binutils Development <binutils@sourceware.org>,
	Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Subject: Re: git is live
Date: Thu, 14 Nov 2013 11:12:00 -0000	[thread overview]
Message-ID: <20131114111140.GF12772@adacore.com> (raw)
In-Reply-To: <5284ACD1.8090609@arm.com>

> > GCC has always allowed vendor branches.  I don't see any reason that
> > binutils/gdb should prohibit them.  Obviously all the code has to be
> > under the GPL or some other explicitly permitted license.
> 
> I believe the GCC policy is that the code must also be assigned to the
> FSF, just as it would be for trunk.

Outside of the policy, I am starting to rethink the policy of
allowing vendor branches. For centralized version control systems
such as SVN, it makes sense, because there is no other choice.

But for decentralized systems such as git, I think vendor branches
could be just as easily hosted elsewhere.  With git, it's really easy
for anyone to host it somewhere, and publish its location. It's also
equally easy for anyone interested in the work to add that location
a remote, and fetch from it.

We could allow exceptions on a case-by-case basis; for instance
we'd allow it if some contributor was constrained by his employer.

But otherwise, everyone who uses the default "fetch" ends up
fetching everything, including vendor branches that they are
not interested in.

-- 
Joel


  reply	other threads:[~2013-11-14 11:12 UTC|newest]

Thread overview: 101+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22  7:01 Tom Tromey
2013-10-22  7:34 ` Andreas Schwab
2013-10-22  7:54 ` Jonas Maebe
2013-10-22  8:04 ` Mark Kettenis
2013-10-22 15:19   ` Tom Tromey
2013-10-22 15:34   ` Eli Zaretskii
     [not found] ` <5266306F.50609@groessler.org>
2013-10-22  8:10   ` Andreas Schwab
2013-10-22  8:21     ` Christian Groessler
2013-10-22  9:59 ` Richard Sandiford
2013-10-22 10:52   ` Fred Cooke
2013-10-22 15:20     ` Tom Tromey
2013-10-22 15:22       ` Fred Cooke
2013-10-22 17:44       ` Pedro Alves
2013-10-22 17:49         ` Jeff Law
2013-10-22 17:51           ` Tom Tromey
2013-10-22 17:57             ` Jeff Law
2013-10-22 18:27           ` Jan-Benedict Glaw
2013-10-22 19:16         ` Andreas Schwab
2013-11-09 18:28           ` Steinar Bang
2013-10-22 15:36   ` Eli Zaretskii
2013-10-22 17:09   ` Jan-Benedict Glaw
2013-10-22 18:41 ` Cary Coutant
2013-10-22 19:07   ` Pedro Alves
2013-10-22 20:41     ` Tom Tromey
2013-10-28 22:35     ` Cary Coutant
2013-10-29  0:37       ` asmwarrior
2013-10-29  1:53       ` Tom Tromey
2013-10-29 18:12         ` Cary Coutant
2013-10-29 19:25           ` Pedro Alves
2013-10-29 19:39             ` Tom Tromey
2014-01-10  2:56               ` Samuel Bronson
2014-01-10  6:53                 ` Eli Zaretskii
2013-10-29  6:33       ` Yao Qi
2013-10-29 19:19       ` Pedro Alves
2013-10-22 18:42 ` Andrew Pinski
2013-10-22 20:42   ` Tom Tromey
2013-10-22 19:19 ` DJ Delorie
2013-10-22 20:43   ` Tom Tromey
2013-10-22 20:46     ` Fred Cooke
2013-10-22 20:50       ` Tom Tromey
2013-10-22 20:57         ` Fred Cooke
2013-10-23  4:58       ` Sergio Durigan Junior
2013-10-23 13:13   ` Tom Tromey
2013-10-23 17:31     ` DJ Delorie
2013-10-23  7:21 ` John Darrington
2013-10-23 13:14   ` Tom Tromey
2013-10-24  5:12     ` John Darrington
2013-10-24  7:30       ` Andreas Schwab
2013-10-24 13:35         ` Paul Smith
2013-10-24  7:36       ` Joel Brobecker
2013-10-24 13:52         ` Tom Tromey
2013-10-24 14:05           ` Tristan Gingold
2013-10-24 14:16             ` Tristan Gingold
2013-10-24 17:05               ` Joel Brobecker
2013-10-24 17:21                 ` Tom Tromey
2013-10-24 17:52                   ` Joel Brobecker
2013-10-25  3:08                     ` Fred Cooke
2013-10-25 12:10                       ` Paul Smith
2013-10-25 12:38                         ` Joel Brobecker
2013-10-25 17:25                           ` John Darrington
2013-10-25 18:27                             ` web sites (was: Re: git is live) Paul Smith
2013-10-23 13:21 ` git is live Gary Benson
2013-10-25 13:51 ` Peter Bergner
2013-10-25 13:55   ` Ian Lance Taylor
2013-11-14 10:58     ` Richard Earnshaw
2013-11-14 11:12       ` Joel Brobecker [this message]
2013-11-14 16:39         ` Eli Zaretskii
2013-11-14 16:55           ` Ian Lance Taylor
2013-11-14 17:21             ` Eli Zaretskii
2013-11-14 17:25             ` H.J. Lu
2013-11-14 18:15               ` Joel Brobecker
2013-11-14 18:25                 ` Andrew Pinski
2013-11-15  7:01                   ` Joel Brobecker
2013-10-25 14:09   ` Fred Cooke
2013-10-25 16:40     ` Peter Bergner
2013-10-25 16:49       ` Fred Cooke
2013-10-25 17:12         ` Peter Bergner
2013-10-25 18:01           ` Tom Tromey
2013-10-25 16:01   ` Tom Tromey
2013-10-25 16:48     ` Peter Bergner
2013-10-29 22:23 ` Alan Modra
2013-10-30  0:37   ` Alan Modra
2013-10-30  1:39   ` Tom Tromey
2013-10-30 13:16     ` Tom Tromey
2013-11-04 18:25 ` H.J. Lu
2013-11-05 14:32   ` Tom Tromey
2013-11-05 14:46     ` Tom Tromey
2013-11-06 17:02       ` H.J. Lu
2013-11-06 17:12         ` Will Newton
2013-11-06 17:22         ` Tom Tromey
2013-11-08 17:29           ` H.J. Lu
2013-11-08 18:04           ` H.J. Lu
2013-11-08 18:34             ` Tom Tromey
2013-11-08 18:43               ` H.J. Lu
2013-11-08 19:09                 ` Tom Tromey
2013-11-08 19:10                 ` Paul Smith
2013-11-08 19:21                   ` Tom Tromey
2013-11-08 19:30                     ` Andreas Schwab
2013-11-08 19:40                       ` Tom Tromey
2013-11-06 19:41 ` Andrew Pinski
2013-11-06 20:01   ` Peter Bergner

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=20131114111140.GF12772@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bergner@vnet.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=iant@google.com \
    --cc=rearnsha@arm.com \
    --cc=tromey@redhat.com \
    --cc=tuliom@linux.ibm.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