git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git fetch --reference?

From
Junio C Hamano <junkio@cox.net>
Date
Nov 15, 2006, 01:49 UTC
Message-ID
<7vu011tr5l.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<f2b55d220611141717r4507c9demddb1cf872dbee073@mail.gmail.com>
"Michael K. Edwards" <medwards.linux@gmail.com> writes:
Show 12 quoted lines
> 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?

For the working trees, if you "fetch" from the tracking tree using short-hand, just like you "fetch" from the origin using short-hand, tags will be followed, I think.

Previous: Michael K. EdwardsNext: Jakub Narebski
Message 4 of 5 in “git fetch --reference?”
  1. Michael K. EdwardsNov 15, 2006
  2. Junio C HamanoNov 15, 2006
  3. Michael K. EdwardsNov 15, 2006
  4. Junio C HamanoNov 15, 2006
  5. Jakub NarebskiNov 15, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.