all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tonton <tonton@riseup.net>
To: Nils Gillmann <ng0@n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] website: Add section section and links to code of conduct
Date: Wed, 16 May 2018 18:17:16 +0200	[thread overview]
Message-ID: <20180516181716.1e6caa1d@merlin.browniehive.net> (raw)
In-Reply-To: <20180516151445.3gznulwkbqvhlzqa@abyayala>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

On Wed, 16 May 2018 15:14:45 +0000
Nils Gillmann <ng0@n0.is> wrote:
> 
> For the website, I have a sxml version of this CoC version. You'd need
> to check which words I added in (I added 3 or 4 extra words I think), but
> if you want to link to it on the website or even include it, could that
> be useful?
> 
That would be great, then it could be added as a page side by side with
contributing and so on. ?

Where can I access it, or would you share it with email or something? Or just
add it and send a patch.

 :)

-- 
I use gpg to sign my emails. All the symbols you may see at the bottom
of this mail is my cryptographic signature. It can be ignored, or used
to check that it really is me sending this email. Learn more by asking
me or see: https://u.fsf.org/zb or https://ssd.eff.org/

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-05-16 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 23:36 [PATCH] website: Add section section and links to code of conduct Tonton
2018-05-16  0:29 ` Tonton
2018-05-16 15:14   ` Nils Gillmann
2018-05-16 16:17     ` Tonton [this message]
2018-05-17 11:43   ` Ludovic Courtès
2018-05-17 13:13     ` Tonton
2018-05-17 21:28     ` Ricardo Wurmus
2018-05-16 15:06 ` Fwd: " rain1
2018-05-16 16:05   ` Tonton
2018-05-17 11:48     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180516181716.1e6caa1d@merlin.browniehive.net \
    --to=tonton@riseup.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 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.