From: Reuben Thomas <rrt@sc3d.org>
To: 11643@debbugs.gnu.org
Subject: bug#11643: Bug fixes in emacs-24
Date: Thu, 7 Jun 2012 12:45:17 +0100 [thread overview]
Message-ID: <CAOnWdoiEzRnsexRFeyF8y+g5t5iTaZszc8S+MacccNiFMef_Uw@mail.gmail.com> (raw)
Is there a policy on what bug fixes will, or can, be moved to the
emacs-24 branch? For example, I just noticed that bug #8954 (flymake
handles read-only directories badly) is not fixed in the branch, and
it looks to me like a straightforward low-impact fix that might be
accepted there.
I don't want to waste maintainers' time with requests for fixes that
won't be ported, hence would appreciate some general advice as well as
an opinion on this particular bug.
--
http://rrt.sc3d.org
next reply other threads:[~2012-06-07 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 11:45 Reuben Thomas [this message]
2012-06-07 12:02 ` bug#11643: Bug fixes in emacs-24 Juanma Barranquero
2012-06-07 12:12 ` Reuben Thomas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOnWdoiEzRnsexRFeyF8y+g5t5iTaZszc8S+MacccNiFMef_Uw@mail.gmail.com \
--to=rrt@sc3d.org \
--cc=11643@debbugs.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.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).