From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Daimrod <daimrod@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-element-context doesn't parse consistently link with spaces
Date: Wed, 05 Mar 2014 16:00:33 +0100 [thread overview]
Message-ID: <87fvmwpu5q.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87y50ok8bc.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 05 Mar 2014 15:51:19 +0100")
Hi Nicolas,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Good question. I have absolutely no clue. OTOH, my tree looks
> up-to-date, and my .git/config reports:
>
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = orgmode@orgmode.org:org-mode.git
> [branch "master"]
> remote = origin
> merge = refs/heads/master
>
> I don't see anything suspicious here.
Well, make sure you did a ~$ make or ~$ make autoloads so that
lisp/org-version.el is correct.
> Also, how comes that master gets a "maint" tag? AFAIU, "release_8.2.5h"
> was put on 53c664c, which belongs to maint.
I always add the release tag on maint, that's where both minor and
major releases are made from (expect that I merge master into maint
before a major release.)
We could have a dedicated tag for the master branch, but for any
move here I'd refer to Achim.
--
Bastien
next prev parent reply other threads:[~2014-03-05 15:01 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 [this message]
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
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=87fvmwpu5q.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=daimrod@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).