From: Nick Dokos <nicholas.dokos@hp.com>
To: Simon Thum <simon.thum@gmx.de>
Cc: Bastien <bzg@gnu.org>, Charles Sebold <Charles.Sebold@lcms.org>,
emacs-orgmode@gnu.org
Subject: Re: Possible bug in parsing / clarification of syntax
Date: Sun, 13 May 2012 12:52:14 -0400 [thread overview]
Message-ID: <6941.1336927934@alphaville> (raw)
In-Reply-To: Message from Simon Thum <simon.thum@gmx.de> of "Sun, 13 May 2012 17:38:40 +0200." <4FAFD580.30104@gmx.de>
Simon Thum <simon.thum@gmx.de> wrote:
> Hi Bastien,
>
> I have not checked master but on maint it still exists. Do you need
> any more details to reproduce?
>
AFAICT, origin/maint is behind origin/master by 512 commits (ymmv depending
on when the last update happened):
$ git log --oneline origin/maint --not origin/master
$ git log --oneline origin/master --not origin/maint | wc -l
512
so I think you'd better check master: main seems way out of date - is it
even used at this point?
Nick
> Cheers,
>
> Simon
>
>
> On 05/08/2012 02:13 PM, Bastien wrote:
> > Hi Simon,
> >
> > Simon Thum<simon.thum@gmx.de> writes:
> >
> >> I have to revoke my earlier statement. The patch does _not_ remove the
> >> TODO_ line from the agenda. I see no change at all.
> >
> > This should be fixed now.
> >
> > Thanks,
> >
>
>
next prev parent reply other threads:[~2012-05-13 16:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 21:30 Possible bug in parsing / clarification of syntax Simon Thum
2012-03-18 17:40 ` David Maus
2012-04-10 17:31 ` Bastien
2012-04-15 20:05 ` Simon Thum
2012-04-16 18:38 ` Simon Thum
2012-05-08 12:13 ` Bastien
2012-05-13 15:38 ` Simon Thum
2012-05-13 16:52 ` Nick Dokos [this message]
2012-05-13 17:56 ` Bastien
2012-05-13 18:11 ` Nick Dokos
2012-05-13 17:54 ` Bastien
2012-05-13 18:48 ` Simon Thum
2012-05-14 14:30 ` Sebold, Charles
2012-05-14 15:15 ` Bastien
2012-05-14 14:29 ` Sebold, Charles
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=6941.1336927934@alphaville \
--to=nicholas.dokos@hp.com \
--cc=Charles.Sebold@lcms.org \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=simon.thum@gmx.de \
/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).