From: "Clément Lassieur" <clement@lassieur.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Email address update
Date: Mon, 27 Aug 2018 14:12:26 +0200 [thread overview]
Message-ID: <87d0u4atzp.fsf@lassieur.org> (raw)
In-Reply-To: <87in3wnj8a.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
>> 1: Just send a patch against all headers you are in and do the .mailmap
>> part as well.
>
> I can do that. Any recommendation for the commit message? I know GNU and Guix
> are quite strict in that regard.
See commit 4a78fd4617908546be15d2c101f5cab512c71f8e :-)
prev parent reply other threads:[~2018-08-27 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 8:52 Email address update Pierre Neidhardt
2018-08-27 11:22 ` Nils Gillmann
2018-08-27 11:26 ` Pierre Neidhardt
2018-08-27 11:37 ` Nils Gillmann
2018-08-27 11:44 ` Pierre Neidhardt
2018-08-27 12:13 ` Clément Lassieur
2018-08-27 12:15 ` Pierre Neidhardt
2018-08-27 12:12 ` Clément Lassieur [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=87d0u4atzp.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).