From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Petton <nicolas@petton.fr>
Cc: 24062@debbugs.gnu.org
Subject: bug#24062: Temporary NEWS markup still in RC
Date: Tue, 23 Aug 2016 17:08:07 +0300 [thread overview]
Message-ID: <83lgznfuig.fsf@gnu.org> (raw)
In-Reply-To: <87mvk3x5gi.fsf@petton.fr> (message from Nicolas Petton on Tue, 23 Aug 2016 10:19:41 +0200)
> From: Nicolas Petton <nicolas@petton.fr>
> Cc: rgm@gnu.org, 24062@debbugs.gnu.org
> Date: Tue, 23 Aug 2016 10:19:41 +0200
>
> Now I see that the ChangeLog I have locally has the following entry:
>
> 2016-08-28 Nicolas Petton <nicolas@petton.fr>
>
> * Version 25.1 released.
>
> See ChangeLog.2 for earlier changes.
>
> So I'm a bit confused, I must have done something wrong, but I can do
> another tarball with this (named RC3). John, Eli, is that what we want?
Making another RC just for ChangeLog changes sounds excessive to me.
I suggest you do that for the final tarball, after we decide to
release 25.1.
Thanks.
next prev parent reply other threads:[~2016-08-23 14:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 18:47 bug#24062: Temporary NEWS markup still in RC Glenn Morris
2016-07-24 18:59 ` Nicolas Petton
2016-07-24 19:01 ` Eli Zaretskii
2016-07-24 19:27 ` Nicolas Petton
2016-08-21 21:34 ` Nicolas Petton
2016-08-22 16:45 ` Glenn Morris
2016-08-22 17:01 ` Nicolas Petton
2016-08-24 5:49 ` Glenn Morris
2016-08-24 8:18 ` Nicolas Petton
2016-08-22 17:07 ` Nicolas Petton
2016-08-22 17:25 ` Eli Zaretskii
2016-08-22 17:41 ` John Wiegley
2016-08-22 19:45 ` Nicolas Petton
2016-08-22 19:54 ` Nicolas Petton
2016-08-23 2:31 ` Eli Zaretskii
2016-08-23 8:15 ` Nicolas Petton
2016-08-23 14:06 ` Eli Zaretskii
2016-08-24 5:44 ` Glenn Morris
2016-08-23 8:19 ` Nicolas Petton
2016-08-23 14:08 ` Eli Zaretskii [this message]
2016-08-23 15:12 ` Nicolas Petton
2016-08-24 5:53 ` Glenn Morris
2016-08-24 8:25 ` Nicolas Petton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lgznfuig.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24062@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.