From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: master 20fa40d: Improve doc for web pages; reproducible tarballs
Date: Mon, 02 Apr 2018 15:13:53 -0400 [thread overview]
Message-ID: <4io9j1h15a.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <5be26af7-8a1d-37d2-9fc3-3039863f845d@cs.ucla.edu> (Paul Eggert's message of "Sun, 1 Apr 2018 13:56:49 -0700")
Thanks.
I think this demonstrates that make-dist should exit with a non-zero
status if the final tar command failed.
next prev parent reply other threads:[~2018-04-02 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180330231211.6450.29690@vcs0.savannah.gnu.org>
[not found] ` <20180330231214.7A6F82041C@vcs0.savannah.gnu.org>
2018-03-31 17:19 ` master 20fa40d: Improve doc for web pages; reproducible tarballs Glenn Morris
2018-04-01 20:56 ` Paul Eggert
2018-04-02 19:13 ` Glenn Morris [this message]
2018-04-09 20:36 ` Paul Eggert
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=4io9j1h15a.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eggert@cs.ucla.edu \
--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).