From: Chong Yidong <cyd@stupidchicken.com>
To: emacs-devel@gnu.org
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: Release branch schedule
Date: Sat, 24 Sep 2011 20:56:22 -0400 [thread overview]
Message-ID: <87ty81l9s9.fsf@stupidchicken.com> (raw)
In-Reply-To: <7600.1316911481@olgas.newt.com> (Bill Wohler's message of "Sat, 24 Sep 2011 17:44:41 -0700")
Bill Wohler <wohler@newt.com> writes:
> Were you planning on cutting a branch when you make the first pretest,
> or are you planning to cut the pretests from the trunk each time?
We will make pretests from the trunk, with a tag for each pretest.
> will trunk be open for business after the first pretest
Yes.
next prev parent reply other threads:[~2011-09-25 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 0:44 Release branch schedule Bill Wohler
2011-09-25 0:56 ` Chong Yidong [this message]
2011-09-25 2:30 ` Bill Wohler
2011-09-25 3:38 ` Chong Yidong
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=87ty81l9s9.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=mh-e-devel@lists.sourceforge.net \
/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).