From: "Michael K. Edwards" <medwards.linux@gmail.com>
To: git@vger.kernel.org
Subject: Re: git fetch --reference?
Date: Tue, 14 Nov 2006 17:17:04 -0800 [thread overview]
Message-ID: <f2b55d220611141717r4507c9demddb1cf872dbee073@mail.gmail.com> (raw)
In-Reply-To: <7vy7qdttc0.fsf@assigned-by-dhcp.cox.net>
On 11/14/06, Junio C Hamano <junkio@cox.net> wrote:
> I am somewhat doubtful that this is common enough to warrant
> adding an extra option to "git fetch", but you could add
> alternates to these new reference object stores before
> initiating the fetch.
> ...
Thanks, that's what I was looking for. I can just set up a "tracking"
tree where I don't attempt any merges, include it in the alternates
for each working tree, and "git fetch" in the tracking tree when it's
convenient. Now, will tags from the tracking tree propagate into the
working trees?
Cheers,
next prev parent reply other threads:[~2006-11-15 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 0:38 git fetch --reference? Michael K. Edwards
2006-11-15 1:02 ` Junio C Hamano
2006-11-15 1:17 ` Michael K. Edwards [this message]
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=f2b55d220611141717r4507c9demddb1cf872dbee073@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).