From: Ricardo Wurmus <rekado@elephly.net>
To: Nils Gillmann <ng0@n0.is>
Cc: guix-devel@gnu.org
Subject: Re: commit 70f57ae00525f6fc919f62aea647a33b29d28537
Date: Thu, 16 Aug 2018 16:53:09 +0200 [thread overview]
Message-ID: <877ekquzvu.fsf@elephly.net> (raw)
In-Reply-To: <20180816073033.yo6pjd5hbhhwtayo@abyayala>
Nils Gillmann <ng0@n0.is> writes:
> This commit is okay, but let's all please refrain from doing future
> corrections like this.
Why?
I prefer consistency, so I’m happy with Tobias’s change.
--
Ricardo
next prev parent reply other threads:[~2018-08-16 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 7:30 commit 70f57ae00525f6fc919f62aea647a33b29d28537 Nils Gillmann
2018-08-16 14:53 ` Ricardo Wurmus [this message]
2018-08-16 15:56 ` Nils Gillmann
2018-08-16 17:03 ` Ricardo Wurmus
2018-08-16 17:13 ` Nils Gillmann
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=877ekquzvu.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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).