From: Joel Brobecker <brobecker@adacore.com>
To: Michael Matz <matz@suse.de>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Sergio Durigan Junior <sergiodj@redhat.com>,
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: Mon, 07 Apr 2014 14:47:00 -0000 [thread overview]
Message-ID: <20140407144720.GH4186@adacore.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1404071623060.23408@wotan.suse.de>
> But it's not necessarily easy for the vendor to _host_ that other
> repository. And IMHO, the current 288 MB for binutils-gdb git objects
> aren't enough to discourage vendor branches (and if you're worried about
> the download size it's equally easy to simply not pull those branches).
I don't think it's "equally easy" to not pull those branches.
If it is, I'd like to have the recipe for "pull all branches except
some", and I will put it on the GDB wiki. On the other hand, there
are many free services on the web to host git repositories. Lastly,
I find that we have way too many branches in our repository at
the moment, drowning the ones that really matter to most (the release
branches, basically). But then again, I also understand that it makes
it easier for people to find that code if they go looking for it.
Hence the not-so-strong objection, although, this issue can be very
easily addressed by documenting those branches on the GDB website or
wiki. It should be anyway, so that people have an idea of what the
branch is about. I think that's what people did with the Archer project.
--
Joel
next prev parent reply other threads:[~2014-04-07 14:47 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 [this message]
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=20140407144720.GH4186@adacore.com \
--to=brobecker@adacore.com \
--cc=aaro.koskinen@iki.fi \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
--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