From: Aaro Koskinen <aaro.koskinen@iki.fi>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
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 19:18:00 -0000 [thread overview]
Message-ID: <20140406191404.GC7558@drone.musicnaut.iki.fi> (raw)
In-Reply-To: <m3vbunyoza.fsf@redhat.com>
Hi,
On Sun, Apr 06, 2014 at 03:02:49AM -0300, Sergio Durigan Junior wrote:
> 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 think it's very useful for users to have all vendor branches
in a single repository. At least with glibc this has helped me a lot
(as a user) when identifying and cherry-picking needed fixes to
my own systems.
A.
next prev parent reply other threads:[~2014-04-06 19:18 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
2014-04-06 19:18 ` Aaro Koskinen [this message]
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=20140406191404.GC7558@drone.musicnaut.iki.fi \
--to=aaro.koskinen@iki.fi \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
--cc=sergiodj@redhat.com \
--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