Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Joel Brobecker <brobecker@adacore.com>
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:27:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1404071623060.23408@wotan.suse.de> (raw)
In-Reply-To: <20140407035120.GA4186@adacore.com>

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.  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).


Ciao,
Michael.


  reply	other threads:[~2014-04-07 14:27 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 [this message]
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=alpine.LNX.2.00.1404071623060.23408@wotan.suse.de \
    --to=matz@suse.de \
    --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=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