emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-element-context doesn't parse consistently link with spaces
Date: Sat, 08 Mar 2014 13:45:48 +0100	[thread overview]
Message-ID: <87zjl0q2o3.fsf@Rainer.invalid> (raw)
In-Reply-To: 87ob1kk74v.fsf@gmail.com

Nicolas Goaziou writes:
> That is what I don't understand. You added "8.2.5h" to "maint", and
> master wasn't merged into "maint" since then. How can the tag
> propagate to "master"?

It doesn't.  But maint is included in master as an ancestor and git
describe uses the most recent tag in common ancestry to label a commit
from.  You can add the option --first-parent to only check tags in the
current branch.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  parent reply	other threads:[~2014-03-08 12:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  8:53 org-element-context doesn't parse consistently link with spaces Daimrod
2014-03-05 13:22 ` Nicolas Goaziou
2014-03-05 13:37   ` Daimrod
2014-03-05 13:45     ` Nicolas Goaziou
2014-03-05 14:12       ` Daimrod
2014-03-05 14:25         ` Nicolas Goaziou
2014-03-05 14:29           ` Bastien
2014-03-05 14:36             ` Daimrod
2014-03-05 15:02               ` Bastien
2014-03-05 15:35                 ` Thorsten Jolitz
2014-03-05 15:42                 ` Nicolas Richard
2014-03-05 16:04                   ` Bastien
2014-03-05 16:27                     ` Nicolas Richard
2014-03-13 15:01                       ` Bastien
2014-03-05 14:51             ` Nicolas Goaziou
2014-03-05 15:00               ` Bastien
2014-03-05 15:16                 ` Nicolas Goaziou
2014-03-05 15:40                   ` Bastien
2014-03-10 14:25                     ` Nicolas Goaziou
2014-03-08 12:45                   ` Achim Gratz [this message]
2014-03-05 14:30           ` Jonathan Leech-Pepin
2014-03-05 14:32           ` Daimrod
2014-03-05 14:52             ` Daimrod

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=87zjl0q2o3.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).