From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Petton <nicolas@petton.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Second Emacs 24.5 pretest next week
Date: Sat, 28 Feb 2015 14:47:40 +0200 [thread overview]
Message-ID: <837fv2td77.fsf@gnu.org> (raw)
In-Reply-To: <87mw3y1b1l.fsf@petton.fr>
> From: Nicolas Petton <nicolas@petton.fr>
> Date: Sat, 28 Feb 2015 13:21:42 +0100
>
> I'll work on another pretest at the end of next week (probably Thursday
> or Friday).
Thank you, I was actually planning to suggest that, given the amount
of changes committed to the branch since you've tarred the previous
pretest.
> Is there anything that should be done prior to the second pretest?
Not that I know of, but maybe someone else does.
next prev parent reply other threads:[~2015-02-28 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 12:21 Second Emacs 24.5 pretest next week Nicolas Petton
2015-02-28 12:47 ` Eli Zaretskii [this message]
2015-02-28 19:04 ` Drew Adams
2015-02-28 19:15 ` Eli Zaretskii
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=837fv2td77.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
/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).