unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-26 updates
Date: Fri, 22 Mar 2019 10:31:04 +0300	[thread overview]
Message-ID: <831s2ztlfr.fsf@gnu.org> (raw)
In-Reply-To: <87o9636bi4.fsf@russet.org.uk> (phillip.lord@russet.org.uk)

> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: Emacs-Devel devel <emacs-devel@gnu.org>
> Date: Thu, 21 Mar 2019 23:41:55 +0000
> 
> Am I free to update the emacs-26/nt/README.W32 file? Someone's just
> pointed out to me that the README on the FTP server (which comes from
> here) is wrong.
> 
> I want to change all the references to the zips, because I have
> simplified the names, as well as describing what the "-no-deps" files
> are. At the moment, the README describes this backwards.
> 
> Should have done this before, but missed it. It probably wouldn't need
> another pre-test as there is no real reason why the README on the
> download site needs to be totally synced with the website.

Please update the README on the FTP site ASAP.

As for the repository, let's wait to see if some other change requires
another RC, and if so, commit the change to the emacs-26 branch.  If
the current RC becomes Emacs 26.2, I'd like to avoid messing up the
release due to this issue.

Thanks.



      reply	other threads:[~2019-03-22  7:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 23:41 Emacs-26 updates Phillip Lord
2019-03-22  7:31 ` Eli Zaretskii [this message]

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=831s2ztlfr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    /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).