From: Eric Bavier <ericbavier@openmailbox.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org,
Help-Guix <help-guix-bounces+ericbavier=openmailbox.org@gnu.org>
Subject: Re: [UX] real names exposed
Date: Mon, 5 Sep 2016 22:09:26 -0500 [thread overview]
Message-ID: <20160905220926.47e7e37b@openmailbox.org> (raw)
In-Reply-To: <87poojihbm.fsf@gnu.org>
On Sun, 04 Sep 2016 21:41:01 +0200
ludo@gnu.org (Ludovic Courtès) wrote:
> While playing with ‘wrap-program’, I rewrote it so create a single
> wrapper and modify that wrapper when it exists instead of layering an
> extra wrapper.
>
> Thoughts? If there are no objections, I’d like to commit this one.
Seems reasonable to me.
`~Eric
next prev parent reply other threads:[~2016-09-06 3:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 18:25 [UX] real names exposed Troy Sankey
2016-08-31 23:11 ` Leo Famulari
2016-08-31 23:33 ` Eric Bavier
2016-09-01 8:59 ` Ludovic Courtès
2016-09-03 15:30 ` Troy Sankey
2016-09-03 22:21 ` Troy Sankey
2016-09-04 19:38 ` Ludovic Courtès
2016-09-03 22:33 ` Ludovic Courtès
2016-09-04 19:41 ` Ludovic Courtès
2016-09-06 3:09 ` Eric Bavier [this message]
2016-09-07 22:04 ` Ludovic Courtès
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=20160905220926.47e7e37b@openmailbox.org \
--to=ericbavier@openmailbox.org \
--cc=help-guix-bounces+ericbavier=openmailbox.org@gnu.org \
--cc=help-guix@gnu.org \
--cc=ludo@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.
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).