zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: Minor "git" irritation
Date: Thu, 20 Jul 2023 09:57:23 +0200	[thread overview]
Message-ID: <20230720075722.555a6fd3ne4uwwnv@sym.noone.org> (raw)
In-Reply-To: <CAH+w=7YF9E00rHJrHCjvi5s1513nG9cx_cm8fvp1qVUk25bVdw@mail.gmail.com>

Hi Bart,

On Wed, Jul 19, 2023 at 10:58:32PM -0700, Bart Schaefer wrote:
> Now "git describe --tags" returns that tag name,

For me, "git describe --tags" usually does _not_ return git tags but
git tags with some information added how far you are away from the
next tag:

  ~/zsh/zsh-upstream → git describe --tags
  local-test-3-g5ec469503

"local-test" is the tag and "3" the amount of commits since then and
"5ec469503" the current HEAD commit id (beginning).

> However, "git tag --delete $(git describe --tags)" says "tag not
> found".

That's to be expected for the above mentioned reasons unless you check
out that tag first.

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

It does not return tags. I think that's the problem here. :-)

		Kind regards, Axel
-- 
PGP: 2FF9CD59612616B5      /~\  Plain Text Ribbon Campaign, http://arc.pasp.de/
Mail: abe@deuxchevaux.org  \ /  Say No to HTML in E-Mail and Usenet
Mail+Jabber: abe@noone.org  X
https://axel.beckert.ch/   / \  I love long mails: https://email.is-not-s.ms/


  reply	other threads:[~2023-07-20  7:57 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 [this message]
2023-07-20  9:41 ` Mikael Magnusson
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:
  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=20230720075722.555a6fd3ne4uwwnv@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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