From: "Michael K. Edwards" <medwards.linux@gmail.com>
To: git@vger.kernel.org
Subject: git fetch --reference?
Date: Tue, 14 Nov 2006 16:38:26 -0800 [thread overview]
Message-ID: <f2b55d220611141638k5f4a0aeas1a43301e4b40bf59@mail.gmail.com> (raw)
When setting up a working area for kernel integration for a new
embedded target, I generally do a "git clone --reference" so that the
new area has its own repository (and its own branch structure) but
most of the blobs come from a local reference copy. But now that I'm
integrating bits from several non-trivially divergent trees (mtd-2.6,
netdev-2.6, linux-2.6.16.y, etc.), it would be nice to avoid
re-downloading blobs for these additional remote branches, which are
also available in the local reference copy. Is it feasible to
implement "git fetch --reference" for this purpose? Or is there a
better way to manage this sort of integration effort?
Cheers,
next reply other threads:[~2006-11-15 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 0:38 Michael K. Edwards [this message]
2006-11-15 1:02 ` git fetch --reference? Junio C Hamano
2006-11-15 1:17 ` Michael K. Edwards
2006-11-15 1:49 ` Junio C Hamano
2006-11-15 1:04 ` Jakub Narebski
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=f2b55d220611141638k5f4a0aeas1a43301e4b40bf59@mail.gmail.com \
--to=medwards.linux@gmail.com \
--cc=git@vger.kernel.org \
/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).