From: Andy Moreton <andrewjmoreton@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs 26.2 RC1 is out!
Date: Thu, 21 Mar 2019 13:48:29 +0000 [thread overview]
Message-ID: <vz136nge3te.fsf@gmail.com> (raw)
In-Reply-To: 87ftrgod5o.fsf@petton.fr
On Thu 21 Mar 2019, Nicolas Petton wrote:
> Philippe Vaucher <philippe.vaucher@gmail.com> writes:
>
>> Is there a branch or a tag on the repository reflecting this version? I
>> couldn't find any, sorry if I missed it.
>
> As it is a release candidate, the tarball contains some changes related
> to the Emacs version being 26.2 and its release date (currently set to
> the 27th) that should not be pushed yet.
A tarball for distribution should not contain anything that has not
been committed to version control.
If you have content that you do not want to appear (yet) on the release
branch, then make a branch for the release candidate, tag a commit on
that branch and the checkout that tag to build the tarball.
> I can push a tag with all committed changes, but the idea is that my
> last commit could be tagged as the release.
Tags are cheap, so there is no reason not to tag the -rc1 build in the
tree, and then tag the actual release later on. If both tags point at
the same commit that is not a problem.
AndyM
next prev parent reply other threads:[~2019-03-21 13:48 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 [this message]
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
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=vz136nge3te.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=emacs-devel@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).