Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: Andreas Schwab <schwab@suse.de>, Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: "matz@suse.de" <matz@suse.de>,
	"brobecker@adacore.com"	<brobecker@adacore.com>,
	"aaro.koskinen@iki.fi" <aaro.koskinen@iki.fi>,
	"sergiodj@redhat.com" <sergiodj@redhat.com>,
	"emachado@linux.vnet.ibm.com"	<emachado@linux.vnet.ibm.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>,
	"binutils@sourceware.org" <binutils@sourceware.org>,
	"bergner@vnet.ibm.com"	<bergner@vnet.ibm.com>,
	"tuliom@linux.vnet.ibm.com"	<tuliom@linux.vnet.ibm.com>
Subject: RE: Vendor branches on sourceware.org's binutils-gdb repo
Date: Mon, 07 Apr 2014 15:16:00 -0000	[thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B023534DD172@LEMAIL01.le.imgtec.org> (raw)
In-Reply-To: <mvmsipp5gdb.fsf@hawking.suse.de>

> > 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.
> 
> git-clone(1):
> 
>        --[no-]single-branch
>            Clone only the history leading to the tip of a single branch,
>            either specified by the --branch option or the primary branch
>            remote’s HEAD points at.

If space is a problem and the purpose of the clone is mainly to perform a
build then you may also be interested in --depth. It comes with a health
warning but really reduces the overheads if it is suitable for you:

       --depth <depth>
           Create a shallow clone with a history truncated to the specified
           number of revisions. A shallow repository has a number of
           limitations (you cannot clone or fetch from it, nor push from 
           nor into it), but is adequate if you are only interested in the
           recent history of a large project with a long history, and would 
           want to send in fixes as patches.

Matthew

  reply	other threads:[~2014-04-07 15:16 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 [this message]
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=6D39441BF12EF246A7ABCE6654B023534DD172@LEMAIL01.le.imgtec.org \
    --to=matthew.fortune@imgtec.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=schwab@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