From: Andreas Enge <andreas@enge.fr>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 5/5] gnu: python-acme: Generate and install documentation.
Date: Thu, 18 Feb 2016 20:36:44 +0100 [thread overview]
Message-ID: <20160218193644.GB2185@solar> (raw)
In-Reply-To: <20160218174650.GC29070@jasmine>
On Thu, Feb 18, 2016 at 12:46:50PM -0500, Leo Famulari wrote:
> I didn't realize that copy-file's return value is unspecified. I've
> found that it does tend to make the whole build fail when the source
> file doesn't exist, so it must be returning #f in that case, right?
Not necessarily. Many things with side-effects just fail with an error
when there is a problem. So in many cases, the question of whether one
needs to explicitly return #t in the end is mainly aesthetic.
Andreas
next prev parent reply other threads:[~2016-02-18 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 3:53 [PATCH 0/5] Install docs for Let's Encrypt Leo Famulari
2016-02-18 3:53 ` [PATCH 1/5] gnu: Add python-sphinxcontrib-programoutput Leo Famulari
2016-02-18 3:53 ` [PATCH 2/5] licenses: Add repoze license Leo Famulari
2016-02-18 3:53 ` [PATCH 3/5] gnu: Add python-sphinx-repoze-autointerface Leo Famulari
2016-02-18 8:28 ` Alex Kost
2016-02-18 17:40 ` Leo Famulari
2016-02-18 3:53 ` [PATCH 4/5] gnu: letsencrypt: Generate and install documentation Leo Famulari
2016-02-18 3:53 ` [PATCH 5/5] gnu: python-acme: " Leo Famulari
2016-02-18 12:51 ` Ricardo Wurmus
2016-02-18 17:46 ` Leo Famulari
2016-02-18 19:36 ` Andreas Enge [this message]
2016-02-20 7:48 ` [PATCH 0/5] Install docs for Let's Encrypt Leo Famulari
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160218193644.GB2185@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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/guix.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).