From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>, Nicolas Petton <nicolas@petton.fr>,
andrewjmoreton@gmail.com, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs 26.2 RC1 is out!
Date: Fri, 22 Mar 2019 11:14:39 +0100 [thread overview]
Message-ID: <CAGK7Mr5DKcJL01s_ifgsTX_L6E6qRHuqQxpQvwJT+tzScbfiJQ@mail.gmail.com> (raw)
In-Reply-To: <83imwbs0ip.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
>
> > > Which are the affected files?
> >
> > README
> > configure.ac
> > etc/HISTORY
> > msdos/sed2v2.inp
> > nt/README.W32
>
> Ah, okay. So the problem is with having these say "26.2" whereas in
> reality 26.2 might need more changes? If so, it doesn't sound a big
> problem to me, but I'd like to hear Glenn's opinion as well.
Just a thought: why not name it 26.2-rc1 in these 26.2-rc1 commits (with a
26.2-rc1 tag)? Then when the final 26.2 is out, rename it to 26.2 and thus
when looking at these files you are always seeing the "latest released"
version.
Maybe that conflicts with other conventions tho, it's just an idea.
Philippe
[-- Attachment #2: Type: text/html, Size: 1089 bytes --]
next prev parent reply other threads:[~2019-03-22 10:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 22:21 Emacs 26.2 RC1 is out! Nicolas Petton
2019-03-21 6:06 ` Van L
2019-03-21 8:22 ` Nicolas Petton
2019-03-21 8:01 ` Philippe Vaucher
2019-03-21 8:16 ` Nicolas Petton
2019-03-21 9:43 ` Philippe Vaucher
2019-03-21 13:48 ` Andy Moreton
2019-03-21 14:45 ` Óscar Fuentes
2019-03-21 20:50 ` Nicolas Petton
2019-03-22 6:55 ` Eli Zaretskii
2019-03-22 8:59 ` Nicolas Petton
2019-03-22 9:11 ` Eli Zaretskii
2019-03-22 9:37 ` Nicolas Petton
2019-03-22 9:48 ` Eli Zaretskii
2019-03-22 9:51 ` Nicolas Petton
2019-03-22 10:00 ` Eli Zaretskii
2019-03-22 10:16 ` Philippe Vaucher
2019-03-22 10:25 ` Eli Zaretskii
2019-03-22 12:32 ` Philippe Vaucher
2019-03-22 10:14 ` Philippe Vaucher [this message]
2019-03-22 11:12 ` Nicolas Petton
2019-03-22 16:39 ` Glenn Morris
2019-03-22 16:46 ` Eli Zaretskii
2019-03-22 16:48 ` Glenn Morris
2019-03-25 9:50 ` Rostislav Svoboda
2019-03-25 10:10 ` Eli Zaretskii
2019-03-25 14:46 ` 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
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=CAGK7Mr5DKcJL01s_ifgsTX_L6E6qRHuqQxpQvwJT+tzScbfiJQ@mail.gmail.com \
--to=philippe.vaucher@gmail.com \
--cc=andrewjmoreton@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
--cc=rgm@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).