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

Re: [PATCH v4.1 5/5] push: update remote tags only with force

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 20, 2012, 05:44 UTC
Message-ID
<7vwqxgsu98.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAEUsAPa9fiF9cuMqRHNsQSz_CsbbvdO-eGDS9HWW3MrAYZPA8w@mail.gmail.com>
Chris Rorvick <chris@rorvick.com> writes:
Show 12 quoted lines
> On Mon, Nov 19, 2012 at 2:23 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> Yeah, this was one of a few stupid mistakes.  Previously I used
> 'forwardable' throughout, but that is awkward except in the last
> commit since until then everything is allowed to fast-forward and the
> flag is only used to output tag-specific advice.  But inverting the
> meaning of the flag is dumb, and I didn't even do it right.
>
> But, as I think you're suggesting, it probably makes more sense to use
> a flag that prevents fast-forwarding when set.  So maybe
> "not_forwardable", or "is_a_tag" => "not_forwardable" if you think the
> renaming is a good idea.

Yeah, calling it not-forwardable from the beginning would be a sensible approach, I would think.

Thanks.
Previous: Chris Rorvick
Message 10 of 10 in “push: update remote tags only with force”
  1. 0/5 push: update remote tags only with forceChris Rorvick, Nov 17, 2012
  2. 1/5 push: return reject reasons via a maskChris Rorvick, Nov 17, 2012
  3. 2/5 push: add advice for rejected tag referenceChris Rorvick, Nov 17, 2012
  4. 3/5 push: flag updatesChris Rorvick, Nov 17, 2012
  5. 4/5 push: flag updates that require forceChris Rorvick, Nov 17, 2012
  6. 5/5 push: update remote tags only with forceChris Rorvick, Nov 17, 2012
  7. 5/5 push: update remote tags only with forceChris Rorvick, Nov 17, 2012
  8. Junio C HamanoNov 19, 2012
  9. Chris RorvickNov 20, 2012
  10. Junio C HamanoNov 20, 2012

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.