unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: JD Smith <jdsmith@as.arizona.edu>
To: emacs-devel@gnu.org
Subject: Pre-release commit etiquette
Date: Wed, 25 Apr 2007 10:28:40 -0700	[thread overview]
Message-ID: <pan.2007.04.25.17.28.33.256770@as.arizona.edu> (raw)


What are the rules for a commit pre-release?  If you have a small bug
fix for the release version, should it:

1. Be added to the branch EMACS_22_BASE, for later merger into HEAD.
2. Be added to both the branch and HEAD.
3. Be added to HEAD only, with a request to merge the change from
   HEAD->EMACS_22_BASE.
4. Be added to HEAD and held for a future release.

If #3, who handles those requests?  I suppose this depends on whether a
new branch is going to be cut at the actual release point, in which case
(I presume), all branch changes will be merged back.

JD

             reply	other threads:[~2007-04-25 17:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 17:28 JD Smith [this message]
2007-04-25 18:22 ` Pre-release commit etiquette Eli Zaretskii
2007-04-26  4:25 ` Richard Stallman
2007-04-26 14:29   ` Stefan Monnier
2007-04-27  1:55     ` Miles Bader
2007-04-27  4:04       ` Stefan Monnier
2007-04-28  3:43         ` Miles Bader
2007-04-28 14:12           ` Stefan Monnier
2007-04-26 15:42   ` JD Smith

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=pan.2007.04.25.17.28.33.256770@as.arizona.edu \
    --to=jdsmith@as.arizona.edu \
    --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).