From: Stephen Berman <stephen.berman@gmx.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Question about commit policy
Date: Fri, 19 Jun 2015 17:17:12 +0200 [thread overview]
Message-ID: <87d20riv7r.fsf@gmx.net> (raw)
In-Reply-To: <jwv381n94f0.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 19 Jun 2015 10:11:01 -0400")
On Fri, 19 Jun 2015 10:11:01 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> I haven't committed any changes or followed the lists very closely for a
>> while, so I'm not up to speed and need clarification. I want to commit
>> a couple of bug fixes for todo-mode.el; the bugs exist on both emacs-24
>> and master, so should I commit to emac-24? CONTRIBUTE says yes, but
>> since AFAICS there has only been one commit to emacs-24 since the
>> release but many bug fix commits to master (maybe all new bugs, I
>> haven't checked), I'm not sure what the current policy is.
>
> You can commit your bugfixes to emacs-24 (but they have to be 100%
> obviously safe), but it's not super important. There's no plan to make
> a new release from the `emacs-24' branch, so the only scenario where
> we'll make use of it, is some kind of big security hole or something
> which creates an urgent need for a new release (with very little
> pretesting, if any).
Thanks. They're safe fixes, so I committed them to emacs-24; hope
Someone™ will merge them to master soon ;-)
Steve Berman
next prev parent reply other threads:[~2015-06-19 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 12:51 Question about commit policy Stephen Berman
2015-06-19 14:11 ` Stefan Monnier
2015-06-19 15:17 ` Stephen Berman [this message]
2015-06-19 23:53 ` Paul Eggert
2015-06-20 9:44 ` Stephen Berman
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=87d20riv7r.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@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 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).