From: Fletcher Charest <fletcher.charest@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Agenda items refer to the wrong headline
Date: Wed, 9 Apr 2014 16:36:22 +0200 [thread overview]
Message-ID: <CAGk6a7n4shFRmO=TDs64NfBOFX=9fDQy+6hh+EHAo5yyAahoDA@mail.gmail.com> (raw)
In-Reply-To: <87r456sj9a.fsf@alphaville.bos.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
Nick, you say you could not reproduce the bug using version
8.2.5h-667-g971dc4, but you did with version 8.2.5h-888-g798bb8d. Just out
of curiosity: does the '888' in '8.2.5h-888-g798bb8d' is a number that is
incremented chronologically? If this is correct (I'm not familiar with this
at all), FWIW, the bug was not caused only by the patch
'8.2.5h-888-g798bb8d', since I observed it also with version
8.2.5h-94-g91175a.
FC
On Wed, Apr 9, 2014 at 3:52 PM, Nick Dokos <ndokos@gmail.com> wrote:
> Nick Dokos <ndokos@gmail.com> writes:
>
> >
> > Starting from release_8.2.5h-888-g798bb8d (this was latest as of this
> > morning) and reverting the above commit fixes Fletcher's problem.
> >
>
> Just to be clear: I'm *not* advocating that the commit be reverted.
> I used the revert just to confirm that something in that patch caused
> the problem that Fletcher observed.
>
> Nick
>
>
>
[-- Attachment #2: Type: text/html, Size: 1432 bytes --]
next prev parent reply other threads:[~2014-04-09 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 4:23 Agenda items refer to the wrong headline Fletcher Charest
2014-04-08 11:53 ` Fletcher Charest
2014-04-17 0:32 ` Bastien
2014-04-08 13:07 ` Nick Dokos
2014-04-08 20:45 ` Fletcher Charest
2014-04-09 3:54 ` Nick Dokos
2014-04-09 13:52 ` Nick Dokos
2014-04-09 14:36 ` Fletcher Charest [this message]
2014-04-10 3:24 ` Nick Dokos
2014-04-14 16:24 ` Fletcher Charest
2014-04-10 3:33 ` Samuel Wales
2014-04-16 19:05 ` Bastien
2014-04-16 22:37 ` Bastien
2014-04-17 0:33 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGk6a7n4shFRmO=TDs64NfBOFX=9fDQy+6hh+EHAo5yyAahoDA@mail.gmail.com' \
--to=fletcher.charest@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.