From: Matt Rice <ratmice@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: matz@suse.de, Joel Brobecker <brobecker@adacore.com>,
aaro.koskinen@iki.fi,
Sergio Durigan Junior <sergiodj@redhat.com>,
emachado@linux.vnet.ibm.com, GDB <gdb@sourceware.org>,
Binutils <binutils@sourceware.org>,
bergner@vnet.ibm.com, tuliom@linux.vnet.ibm.com
Subject: Re: Vendor branches on sourceware.org's binutils-gdb repo
Date: Wed, 09 Apr 2014 01:49:00 -0000 [thread overview]
Message-ID: <CACTLOFpGNYHiJqcJsHAo5b6AycH5hjJWmk3w8n7VDx9jvWeE5Q@mail.gmail.com> (raw)
In-Reply-To: <201404071452.s37EqLB9024528@glazunov.sibelius.xs4all.nl>
On Mon, Apr 7, 2014 at 7:52 AM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> Date: Mon, 7 Apr 2014 16:27:22 +0200 (CEST)
>> From: Michael Matz <matz@suse.de>
>>
>> Hi,
>>
>> On Sun, 6 Apr 2014, Joel Brobecker wrote:
>>
>> > > 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.
>> >
>> > FWIW: I have found that the extra branches are just making me download
>> > lots of commits that I have no use for, and I suspect that this is the
>> > case for many of us. That's the default behavior, and most users will be
>> > impacted by those. While it's convenient, it is also very easy to pull a
>> > branch from another repository.
>>
>> But it's not necessarily easy for the vendor to _host_ that other
>> repository.
>
> Really? Are there really companies that are active in the Free
> Software community that don't have the infrastructure to host a
> relatively small git repo?
I generally prefer working in the distributed model, but I think it
makes sense for sourceware to host it, for copyright assignment
purposes
it makes it clear and easy to decide if effort on a branch can be
merged by a third party into master, which happens on occasion.
I would probably be happier if there was a separate repository
binutils+gdb-vendor.git or some such though.
next prev parent reply other threads:[~2014-04-09 1:49 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
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 [this message]
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=CACTLOFpGNYHiJqcJsHAo5b6AycH5hjJWmk3w8n7VDx9jvWeE5Q@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=matz@suse.de \
--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