From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: What's the convention for committing bug fixes?
Date: Thu, 17 Apr 2014 18:50:15 +0000 [thread overview]
Message-ID: <20140417185015.GA3423@acm.acm> (raw)
Hello, Emacs.
For bug fixes which should go into both Emacs 24.4 and the trunk, where
should they be committed? Into the 24.4 branch, into the trunk, or into
both?
For recent previous releases, the convention was to commit to the
release branch and somebody dedicated and energetic copied the commit to
the trunk.
Sorry if this has already been discussed and I somehow missed it.
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2014-04-17 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 18:50 Alan Mackenzie [this message]
2014-04-17 20:01 ` What's the convention for committing bug fixes? Eli Zaretskii
2014-04-17 22:17 ` Alan Mackenzie
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=20140417185015.GA3423@acm.acm \
--to=acm@muc.de \
--cc=emacs-devel@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).