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

Re: [PATCH 07/11] git-fetch: Limit automated tag following to only fetched objects

From
CJ van den Berg <cj@vdbonline.com>
Date
Nov 9, 2007, 12:12 UTC
Message-ID
<20071109121228.GA4241@prefect.vdbonline.net>
In-Reply-To
<20071109110631.GG19368@spearce.org>
On Fri, Nov 09, 2007 at 06:06:31AM -0500, Shawn O. Pearce wrote:
> We now redefine the rule to be: "tags are fetched if they refer
> to an object that was just transferred; that is an object that is
> new to your repository".  This rule is quite simple to understand,
> you only get a tag if you just got the object it refers to.

With this new rule a retrospectively pushed tag will never be fetched, right? With our local work flow tags are only ever pushed retrospectively because the tagged commit has to first pass regression tests. So this would be a major regression for us.

I think adding a temporal dependency between the pushing and fetching of branches and tags in this way is likely to cause even more confusing and apparently random behaviour. 

-- 
CJ van den Berg

mailto:cj@vdbonline.com
  xmpp:cj@vdbonline.com
Previous: Johannes SixtNext: Andreas Ericsson
Message 3 of 6 in “git-fetch: Limit automated tag following to only fetched objects”
  1. 07/11 git-fetch: Limit automated tag following to only fetched objectsShawn O. Pearce, Nov 9, 2007
  2. Johannes SixtNov 9, 2007
  3. CJ van den BergNov 9, 2007
  4. Andreas EricssonNov 10, 2007
  5. Junio C HamanoNov 9, 2007
  6. Shawn O. PearceNov 11, 2007

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.