From: Jeff King <peff@peff.net>
To: Howard Chu <hyc@symas.com>
Cc: git@vger.kernel.org
Subject: Re: Wishlist: git fetch --reference
Date: Fri, 22 Aug 2014 00:20:57 -0400 [thread overview]
Message-ID: <20140822042057.GD27992@peff.net> (raw)
In-Reply-To: <53F6B1AB.3030706@symas.com>
On Thu, Aug 21, 2014 at 07:57:47PM -0700, Howard Chu wrote:
> I maintain multiple copies of the same repo because I keep each one checked
> out to different branch/rev levels. It would be nice if, similar to clone
> --reference, we could also use git fetch --reference to reference a local
> repo when doing a fetch to pull in updates.
I think it is just spelled:
echo $reference_repo >>.git/objects/info/alternates
git fetch
We need "--reference" with clone because that first line needs to happen
after clone runs "git init" but before it runs "git fetch". And if you
cloned with --reference, of course, the alternates file remains and
further fetches will automatically use it.
-Peff
next prev parent reply other threads:[~2014-08-22 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 2:57 Wishlist: git fetch --reference Howard Chu
2014-08-22 4:20 ` Jeff King [this message]
2014-08-22 5:25 ` Howard Chu
2014-08-22 7:01 ` Dennis Kaarsemaker
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=20140822042057.GD27992@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=hyc@symas.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;
as well as URLs for NNTP newsgroup(s).