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

Re: git fetch refs and tags

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 23, 2013, 14:59 UTC
Message-ID
<7vsj2hl2c7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1366714421.2899.10.camel@lws-weitzel>
Jan Weitzel <J.Weitzel@phytec.de> writes:
Show 8 quoted lines
> Hello,
> I have the following problem: I have 2 bare git repositories one has
> several branches and tags.
> If I try this in the second repository:
> git fetch -f ../main.git refs/heads/master:refs/heads/master 
> I'm getting also tags from other branches, if I have an old object from
> one of the other branches.
> I would expect to have only tags pointing to master ref.

A tag that points at a commit that is reachable from 'master' will be followed, not just pointing _at_ 'master'. For example, when your 'master' is a bit beyond v1.2 release, it is likely you will also get v1.1 and v1.0 tags (if your release structure is such that new release contains everything old releases had).

Previous: Johan HerlandNext: Johan Herland
Message 5 of 7 in “git fetch refs and tags”
  1. Jan WeitzelApr 23, 2013
  2. Johan HerlandApr 23, 2013
  3. Jan WeitzelApr 23, 2013
  4. Johan HerlandApr 23, 2013
  5. Junio C HamanoApr 23, 2013
  6. Johan HerlandApr 23, 2013
  7. Jan WeitzelApr 24, 2013

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.