git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Justin Tobler <jltobler@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] tag: allow idempotent "git tag" without "--force"
Date: Fri, 11 Jul 2025 14:40:44 -0700	[thread overview]
Message-ID: <xmqqcya6z9r7.fsf@gitster.g> (raw)
In-Reply-To: <dt5ruadvr7lmhsbypmb6yili5cookfx5btw4gzfeui7ehxxajv@ziael4udbbcy> (Justin Tobler's message of "Fri, 11 Jul 2025 15:57:00 -0500")

Justin Tobler <jltobler@gmail.com> writes:

> For example push the newly created tag:
>
>   git tag T O && git push --tags

The above is not quite a scalable workflow and is not recommendable,
though.  What if you are publishing to more than one place, and/or
sometimes some of them are not reachable?  You want to push out your
tag not because you newly created it, but because you know some
remotes may not have it for whatever reason.  "I just created one"
is a crude approximate for the latter.  "Last time I created one, it
somehow failed to push out" (so I have to try again) needs to be
considered.

Having said that, ever since I invented "push --follow-tags", I
rarely push tags out just for the sake of pushing them out.  Only
when the real contents that matter are pushed out, tags that point
at them would follow.

> To me atleast, the feedback of knowing whether tag was created seems a bit more
> interesting. I also don't feel super strongly though.

I do not fell strongly one way or anothre, either.  Discarding the
topic is easier than keeping it for me, so let me mark it for trash
bin.

Thanks.

      reply	other threads:[~2025-07-11 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09  7:00 Suggestion: error "tag ... already exists" should distinguish between tagging different or same commit: M Hickford
2025-06-09 18:42 ` Junio C Hamano
2025-06-09 19:37   ` Hilco Wijbenga
2025-06-09 20:15     ` Andreas Schwab
2025-06-09 20:19     ` Junio C Hamano
2025-06-09 21:03       ` Hilco Wijbenga
2025-06-10  7:00   ` M Hickford
2025-06-10 14:51     ` Junio C Hamano
2025-07-07 22:24       ` Junio C Hamano
2025-07-07 23:12         ` rsbecker
2025-07-11 19:08           ` Junio C Hamano
2025-07-11 19:10       ` [PATCH] tag: allow idempotent "git tag" without "--force" Junio C Hamano
2025-07-11 20:57         ` Justin Tobler
2025-07-11 21:40           ` Junio C Hamano [this message]

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=xmqqcya6z9r7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.com \
    /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).