From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: matz@suse.de
Cc: brobecker@adacore.com, aaro.koskinen@iki.fi, sergiodj@redhat.com,
emachado@linux.vnet.ibm.com, gdb@sourceware.org,
binutils@sourceware.org, bergner@vnet.ibm.com,
tuliom@linux.vnet.ibm.com
Subject: Re: Vendor branches on sourceware.org's binutils-gdb repo
Date: Mon, 07 Apr 2014 14:52:00 -0000 [thread overview]
Message-ID: <201404071452.s37EqLB9024528@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.1404071623060.23408@wotan.suse.de> (message from Michael Matz on Mon, 7 Apr 2014 16:27:22 +0200 (CEST))
> 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?
> 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).
Size is an issue for me. I try to support GDB on many platforms, some
of which are somewhat old or low power and don't have a lot of disk
storage. I'm already running into problems on some of my machines.
And every time git messes up my repo because I run out of disk space
(or just because it doesn't seem to properly implement DWIM) I need to
fetch everything all over again.
So how do I tell git to only clone master and not give me everybody
else's shit? Last time I tried to do that, it simply didn't work.
next prev parent reply other threads:[~2014-04-07 14:52 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 [this message]
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=201404071452.s37EqLB9024528@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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=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