From: Andy Wingo <wingo@igalia.com>
To: Andy Patterson <ajpatter@uwaterloo.ca>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] services: cups: Follow symlinks when installing extensions.
Date: Thu, 01 Dec 2016 11:04:35 +0100 [thread overview]
Message-ID: <cucinr4x8wc.fsf@igalia.com> (raw)
In-Reply-To: <20161130161745.136f7c1f@uwaterloo.ca> (Andy Patterson's message of "Wed, 30 Nov 2016 16:17:45 -0500")
Hi,
On Wed 30 Nov 2016 22:17, Andy Patterson <ajpatter@uwaterloo.ca> writes:
> This small patch fixes a build error I encountered when adding hplip to
> my cups-configuration-extensions.
Thanks, applied. In a better world, all these CUPS packages will be not
doing so much symlinking in their output dirs, but the perfect is the
enemy of the good :)
Andy
prev parent reply other threads:[~2016-12-01 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 21:17 [PATCH] services: cups: Follow symlinks when installing extensions Andy Patterson
2016-12-01 10:04 ` Andy Wingo [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cucinr4x8wc.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=ajpatter@uwaterloo.ca \
--cc=guix-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/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).