From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Subject: email change to the generic @no-reply.pragmatique.xyz format
Date: Sun, 9 Apr 2017 11:11:37 +0000 [thread overview]
Message-ID: <20170409111137.s55yyfpzkm2s6rhf@abyayala> (raw)
Hi,
Regard this as an heads-up email:
As communicated off-list with Ludovic prior to this message, I give
people who contribute to any current and future subproject of
pragmatique the option to use "theirname@no-reply.pragmatique.xyz" email
addresses. We currently run no Email server at the domain, but I will
add one at some point in the next months (so that eventually some names
can resolve when you remove the no-reply in the email, as an optional
case).
I realize that the patches need to be send somehow anyway, but that's an
entire different matter up for discussion on our side.
This address is used to reduce metadata, is not up for discussion and I
hope you respect my decision.
Personally not all packages I work on are relevant for pragmatique but
this is hard to communicate to git log, which is why I have switched my
git email address to this format.
Of course this means I have to make changes to the .mailmap eventually
for my name+email couple again.
This domain is payed for, and will stick around.
In case a bug is found, a package is found to be problematic etc which
was caused by someone with an @no-reply.pragmatique.xyz address, you can
use the pragmatique@inventati.org to reach out.
In case the list address should ever change you can find the current one
on https://pragmatique.xyz/ and I will communicate any changes to you.
As people sometimes need PGP keys, I've gone back to including my
contact page in the signature.
By the way:
You can also find "ng0@no-reply.pragmatique.xyz" on the keyservers as
I'm already signing my commits to gnunet development with it for a while
now.
Thanks,
ng0
--
PGP and more: https://people.pragmatique.xyz/ng0/
reply other threads:[~2017-04-09 11:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170409111137.s55yyfpzkm2s6rhf@abyayala \
--to=contact.ng0@cryptolab.net \
--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).