From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Petton <nicolas@petton.fr>
Cc: rgm@gnu.org, andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs 26.2 RC1 is out!
Date: Fri, 22 Mar 2019 09:55:55 +0300 [thread overview]
Message-ID: <83a7hntn2c.fsf@gnu.org> (raw)
In-Reply-To: <87o964kl4p.fsf@petton.fr> (message from Nicolas Petton on Thu, 21 Mar 2019 21:50:14 +0100)
> From: Nicolas Petton <nicolas@petton.fr>
> Date: Thu, 21 Mar 2019 21:50:14 +0100
> Cc: rgm@gnu.org
>
> I'm putting Glenn in Cc, I believe he wrote that part of the
> documentation.
>
> > A tarball for distribution should not contain anything that has not
> > been committed to version control.
>
> I agree with that, but it's not the current process as described in
> admin/make-tarball.txt. I'm fine with tagging RCs and pushing files
> with unreleased version numbers, but then I will adjust the content of
> make-tarball.txt.
Can you (or Glenn or someone else) describe what would need to be
changed in the docs, and what additional actions would have to be
made?
I don't think I mind RC tags in the repository, even if they
eventually point to the same commit as the release, but I'm not sure I
understand the details well enough.
Thanks.
next prev parent reply other threads:[~2019-03-22 6:55 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 [this message]
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
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=83a7hntn2c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--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).