Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Cc: GDB <gdb@sourceware.org>, Binutils <binutils@sourceware.org>,
	       Peter Bergner <bergner@vnet.ibm.com>,
	       Tulio Magno Quites Machado Filho
	<tuliom@linux.vnet.ibm.com>
Subject: Re: Vendor branches on sourceware.org's binutils-gdb repo
Date: Sun, 06 Apr 2014 06:02:00 -0000	[thread overview]
Message-ID: <m3vbunyoza.fsf@redhat.com> (raw)
In-Reply-To: <53406399.9050303@linux.vnet.ibm.com> (Edjunior Barbosa Machado's	message of "Sat, 05 Apr 2014 17:12:09 -0300")

On Saturday, April 05 2014, Edjunior Barbosa Machado wrote:

> Hi all,

Hey :-).

> We already maintain community vendor branches for glibc (on
> sourceware.org) and gcc (on gnu.org), and we'd like to do the same for
> binutils-gdb. The idea is to create separate namespaces, i.e.
> ibm/gdb/7.7 and ibm/binutils/2.24. Those branches will only store
> patches under GPL and with a proper copyright assignment.
>
> Any comments? Objections?

Hm, just a comment, but nothing major or blocker.  I understand the need
for vendor branches, but I also think that we should make more use of
git's distributed model.  For example, why can't Company X (I am not
criticizing anyone particularly, really) create and maintain its own git
repository, with all the necessary branches there?  Wouldn't that be
better than (a) "polluting" sourceware's repository and (b) putting an
extra pressure on sourceware's infra?

I may be missing some detail here, and if that is the case then I am
sorry for creating unecessary noise, but at first glance I couldn't come
up with a decent answer for my question above.

P.S.: Before I forget, this comment/question really applies to everyone
who is still using sourceware as their "personal" git repo.

P.S. 2: It is also worth mentioning that my intention is *not* to make
people create GitHub accounts and start doing things there.  Aside from
the fact that GitHub uses non-free software to run its services (and
also serves non-free Javascript), IMHO it also encourages people to stay
within its "social network" walls and makes it a little harder to get
advantage from git's distributed protocol.

-- 
Sergio


  reply	other threads:[~2014-04-06  6:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05 20:12 Edjunior Barbosa Machado
2014-04-06  6:02 ` Sergio Durigan Junior [this message]
2014-04-06 19:18   ` Aaro Koskinen
2014-04-07  3:51     ` Joel Brobecker
2014-04-07 14:27       ` Michael Matz
2014-04-07 14:47         ` Joel Brobecker
2014-04-07 15:41           ` Markus Trippelsdorf
2014-04-07 14:52         ` Mark Kettenis
2014-04-07 15:06           ` Andreas Schwab
2014-04-07 15:16             ` Matthew Fortune
2014-04-07 15:39             ` Mark Kettenis
2014-04-07 15:43               ` Andreas Schwab
2014-04-07 15:44               ` Michael Matz
2014-04-07 15:41           ` Michael Matz
2014-04-07 15:46             ` Joel Brobecker
2014-04-07 15:48             ` Andreas Schwab
2014-04-09  1:49           ` Matt Rice
2014-04-09 12:46             ` Joel Brobecker
2014-04-08 23:17 ` Mike Frysinger
2014-04-09 17:58 ` Stan Shebs
2014-04-09 18:41   ` Doug Evans
2016-06-27 19:15 ` Mike Frysinger

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=m3vbunyoza.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=bergner@vnet.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=emachado@linux.vnet.ibm.com \
    --cc=gdb@sourceware.org \
    --cc=tuliom@linux.vnet.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