all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gregor Zattler <grfz@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 17724@debbugs.gnu.org
Subject: bug#17724: 24.4.50; regression: error "`recenter'ing a window that does not display current-buffer." when opening org-mode file
Date: Wed, 18 Jun 2014 20:52:05 +0200	[thread overview]
Message-ID: <20140618185205.GA19722@boo.workgroup> (raw)
In-Reply-To: <jwvioocfc04.fsf-monnier+emacsbugs@gnu.org>

Hi Stefan,
* Stefan Monnier <monnier@iro.umontreal.ca> [07. Jun. 2014]:
> BTW, I would also point out that people who do not actively develop
> Emacs should ideally use the emacs-24 (i.e. 24.3.9x) branch now rather
> than the trunk (24.4.50), so as to help us fix problems before the
> 24.4 release.

I'd love to.  But the emacs-24 branch gives emacs version 24.4.50,
there is a tag emacs-24.3.91 tough, which is from 2014-05-11, whilst
the emacs-24 branch ATM has commits from 2014-06-07.

I'm a novice to version control, but I think a release-branch (as Eli
mentiones in mid:83y4wuth7s.fsf@gnu.org) would be great and I think
it's doable with a normal branch!?

Ciao; Gregor





  parent reply	other threads:[~2014-06-18 18:52 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07 15:57 bug#17724: 24.4.50; regression: error "`recenter'ing a window that does not display current-buffer." when opening org-mode file Gregor Zattler
2014-06-07 16:26 ` Eli Zaretskii
2014-06-07 17:18   ` Glenn Morris
2014-06-07 18:59     ` Bastien
2014-06-09 20:53       ` Nicolas Richard
2014-06-09 20:53       ` Nicolas Richard
2014-06-10  2:38         ` Eli Zaretskii
2014-06-10  8:09           ` Nicolas Richard
2014-06-10  8:09           ` Nicolas Richard
2014-06-10  8:19             ` Bastien
2014-06-17 12:14               ` lee
2014-06-17 12:14               ` lee
2014-06-17 13:20                 ` Stefan Monnier
2014-06-17 13:20                 ` Stefan Monnier
2014-06-17 17:15                   ` lee
2014-06-17 19:28                     ` Eli Zaretskii
2014-06-18 11:10                       ` lee
2014-06-19  2:46                         ` Eli Zaretskii
2014-06-19  9:35                           ` lee
2014-06-19  9:35                           ` lee
2014-06-19  2:46                         ` Eli Zaretskii
2014-06-18 11:10                       ` lee
2014-06-17 19:28                     ` Eli Zaretskii
2014-06-17 19:45                     ` Stefan Monnier
2014-06-17 19:45                     ` Stefan Monnier
2014-06-18  2:43                       ` Eli Zaretskii
2014-06-18  2:43                       ` Eli Zaretskii
2014-06-18 12:04                         ` Stefan Monnier
2014-06-18 14:39                           ` Eli Zaretskii
2014-06-18 14:39                           ` Eli Zaretskii
2014-06-18 18:15                             ` Stefan Monnier
2014-06-18 18:15                             ` Stefan Monnier
2014-06-18 12:04                         ` Stefan Monnier
2014-06-17 17:15                   ` lee
2014-06-10  8:19             ` Bastien
2014-06-10  2:38         ` Eli Zaretskii
2014-06-07 18:59     ` Bastien
2014-06-07 17:18   ` Glenn Morris
2014-06-08  1:06 ` Stefan Monnier
2014-06-18 18:52   ` Gregor Zattler
2014-06-18 18:52   ` Gregor Zattler [this message]
2014-06-18 19:10     ` Eli Zaretskii
2014-06-18 22:07       ` Gregor Zattler
2014-06-18 22:07       ` Gregor Zattler
2014-06-19  8:20         ` Nicolas Richard
2014-06-19 14:58           ` Eli Zaretskii
2014-06-19 14:58           ` Eli Zaretskii
2014-06-19 19:08           ` Gregor Zattler
2014-06-19 19:08           ` Gregor Zattler
2014-06-19 20:29             ` Nicolas Richard
2014-06-19 20:29             ` Nicolas Richard
2014-06-19  8:20         ` Nicolas Richard
2014-06-19 20:43         ` Achim Gratz
2014-06-19 20:43         ` Achim Gratz
2014-06-18 19:10     ` Eli Zaretskii
2014-06-08  1:06 ` Stefan Monnier

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=20140618185205.GA19722@boo.workgroup \
    --to=grfz@gmx.de \
    --cc=17724@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.