git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Voie, Per Erlend Torbergsen" <Per.Erlend.Voie@dnvgl.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: git describe returns tags including 'refs/tags/
Date: Tue, 24 Oct 2017 08:12:49 +0000	[thread overview]
Message-ID: <DB6PR0202MB28074CB67408334285264588A4470@DB6PR0202MB2807.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <DB6PR0202MB2807FB243E7D7A574D555F16A4470@DB6PR0202MB2807.eurprd02.prod.outlook.com>

Hi

I am versioning my python package using git tags and the python-versioneer package.

Basically versioneer gets the version number from git tags using the command "git describe --tags --dirty --always --long --match 'tag_prefix*'". I do not apply a tag prefix, hence tag_prefix=''.

Now to the problem. My build breaks because the command above returns tags like this "refs/tags/2.12.2" which contains invalid characters. Actually, it seems that executing the command above reconfigured the way git describe behaves.

because, before running the above command "git describe --tags --dirty" returned

2.12.2-17-gd8e62f9

After, "git describe --tags --dirty" returns

warning: tag 'refs/tags/2.12.2' is really '2.12.2' here
refs/tags/2.12.2-17-gd8e62f9

Is it so that "git describe --tags --dirty --always --long --match 'tag_prefix*'" changes the way git describe behave or am I missing something? If it does, how can I reset it?

Thanks
Per

**************************************************************************************
This e-mail and any attachments thereto may contain confidential information and/or information protected by intellectual property rights for the exclusive attention of the intended addressees named above. If you have received this transmission in error, please immediately notify the sender by return e-mail and delete this message and its attachments. Unauthorized use, copying or further full or partial distribution of this e-mail or its contents is prohibited.
**************************************************************************************

           reply	other threads:[~2017-10-24  8:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DB6PR0202MB2807FB243E7D7A574D555F16A4470@DB6PR0202MB2807.eurprd02.prod.outlook.com>]

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=DB6PR0202MB28074CB67408334285264588A4470@DB6PR0202MB2807.eurprd02.prod.outlook.com \
    --to=per.erlend.voie@dnvgl.com \
    --cc=git@vger.kernel.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://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).