From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH][rfc][doc] extending the contribution guidelines
Date: Sun, 24 Jul 2016 19:58:16 +0200 [thread overview]
Message-ID: <87wpkaapfr.fsf@gnu.org> (raw)
In-Reply-To: <87lh0uamuo.fsf@we.make.ritual.n0.is> (ng0@we.make.ritual.n0.is's message of "Thu, 21 Jul 2016 18:05:03 +0000")
ng0 <ng0@we.make.ritual.n0.is> skribis:
> We have no documentation on wether using a legal name for
> contributions is required or not and if name changes are okay.
Commit dfcdd9c25d552fb2691552837b2f2f50bb0b14fb clarifies that.
Ludo’.
prev parent reply other threads:[~2016-07-24 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 18:05 [PATCH][rfc][doc] extending the contribution guidelines ng0
2016-07-23 13:57 ` Andreas Enge
2016-07-24 16:55 ` Ludovic Courtès
2016-07-24 17:58 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpkaapfr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.