help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Minor "git" irritation
Date: Thu, 20 Jul 2023 11:41:02 +0200	[thread overview]
Message-ID: <CAHYJk3SrDiMrMS8zng4U9zBMhH=zPyeBv7woZFDHwP1i2NYuqg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7YF9E00rHJrHCjvi5s1513nG9cx_cm8fvp1qVUk25bVdw@mail.gmail.com>

On 7/20/23, Bart Schaefer <schaefer@brasslantern.com> wrote:
> At some point in the past I tagged a revision in my local clone so that I
> could easily run diffs against that initial state.
> Now "git describe --tags" returns that tag name, which ends up in
> $ZSH_PATCHLEVEL, which is not correct. "git fetch --tags" does not change
> this.

Perhaps we should change the code in Makefile to not use git describe
--tags; without --tags it will only use annotated or signed tags,
which we do use for release tags. You would almost never annotate a
throwaway tag like the one you created so it should be correct in more

> However, "git tag --delete $(git describe --tags)" says "tag not found".  I
> don't know how it's possible for describe to return a tag that doesn't
> exist, or how it got that way, but here I am.
> How do I get rid of that tag?  I've read the doc for "git fetch --prune
> --prune-tags" but that sounds as if it'll remove other local references
> that don't exist on the origin, which is not what I want.

Like the other reply said, you want just the name of the tag, so if
your ZSH_PATCHLEVEL is sometag-293-g238abc then you want just "git tag
-d sometag", you should also be able to tab complete it :).

Mikael Magnusson

  parent reply	other threads:[~2023-07-20  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20  5:58 Bart Schaefer
2023-07-20  7:57 ` Axel Beckert
2023-07-20  9:41 ` Mikael Magnusson [this message]
2023-07-26  2:17   ` Bart Schaefer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHYJk3SrDiMrMS8zng4U9zBMhH=zPyeBv7woZFDHwP1i2NYuqg@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \


* 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.
Code repositories for project(s) associated with this public inbox


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).