From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org release 7.8.08 (BUGFIX-only release)
Date: Wed, 04 Apr 2012 21:36:40 +0200 [thread overview]
Message-ID: <87ty0zz3uf.fsf@Rainer.invalid> (raw)
In-Reply-To: 87398km10m.fsf@gnu.org
Bastien writes:
> Not sure I understand: the tag release_7.8.08 *is* on the server and was
> pushed from the maint branch (see http://orgmode.org/w/org-mode.git).
Git has two types of tags: lightweight, which really aren't much more
than a different way to mark the head of a tree without actually
creating a branch at that point. The second kind is the annotated one,
which is more like a commit - it comes with a description like a commit,
just not with a change set.
> Do you mean I need to annotate it? (I will do.)
Yes, from the git-tag man page:
By default (without --all or --tags) git describe only shows annotated
tags. For more information about creating annotated tags see the -a
and -s options to git-tag(1).
This is a peculiar choice, but it makes much sense when considering that
release tags would almost always be annotated ones (they could carry the
changelog between releases for instance). Now if you use only
lightweight tags for keeping track of various points in you Git history
by name, git describe will still pick up the release tags and not your
nilly-willy ones.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
prev parent reply other threads:[~2012-04-04 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 16:41 Org release 7.8.08 (BUGFIX-only release) Bastien
2012-04-02 18:07 ` Chris Randle
2012-04-02 18:18 ` Bastien
2012-04-02 18:21 ` Achim Gratz
2012-04-03 17:17 ` Achim Gratz
2012-04-04 7:03 ` Bastien
2012-04-04 19:36 ` Achim Gratz [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ty0zz3uf.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.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.savannah.gnu.org/cgit/emacs/org-mode.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).