unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jonathan McHugh" <indieterminacy@libre.brussels>
To: "Tissevert" <tissevert+guix@marvid.fr>,
	"Tobias Geerinckx-Rice" <me@tobias.gr>
Cc: Guix Devel <guix-devel@gnu.org>, zimoun <zimon.toutoune@gmail.com>
Subject: Re: Update CoC adapted from upstream 2.1 (instead of 1.4)
Date: Fri, 25 Feb 2022 08:16:11 +0000	[thread overview]
Message-ID: <87a433439d3981b1bb1efb4706029473@libre.brussels> (raw)
In-Reply-To: <20220225084711.36619a98@marvid.fr>

February 25, 2022 8:48 AM, "Tissevert" <tissevert+guix@marvid.fr> wrote:

> Are dickpics going to be necessary to sign commits from now on ?

Well, we cant be mandating binary commits now can we?!? This is Guix FFS.

Cmon, if I wanted to be perusing dicks and commits Id be on other mailing lists.

Lets move on. Please.


Jonathan


  parent reply	other threads:[~2022-02-25 10:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25  0:05 Update CoC adapted from upstream 2.1 (instead of 1.4) zimoun
2022-02-25  0:09 ` Tobias Geerinckx-Rice
2022-02-25  7:47   ` Tissevert
2022-02-25  8:26     ` zimoun
2022-02-25  9:38     ` Thorsten Wilms
2022-02-25  8:16   ` Jonathan McHugh [this message]
2022-02-25 16:59 ` Taylan Kammer
2022-02-25 20:38   ` Philip McGrath
2022-02-25 20:50     ` Taylan Kammer
2022-02-25 22:05 ` Apology and proposal withdraw zimoun
2022-02-26  0:48 ` Update CoC adapted from upstream 2.1 (instead of 1.4) Liliana Marie Prikler
2022-02-26  1:20   ` Tobias Geerinckx-Rice
2022-02-26  9:08   ` Thorsten Wilms
2022-02-26 18:17     ` elais
  -- strict thread matches above, loose matches on Subject: below --
2022-02-25 15:18 Blake Shaw
2022-02-25 17:29 ` Taylan Kammer
2022-02-25 19:29   ` Ryan Sundberg via Development of GNU Guix and the GNU System distribution.
2022-02-25 22:20 Blake Shaw

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=87a433439d3981b1bb1efb4706029473@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    --cc=tissevert+guix@marvid.fr \
    --cc=zimon.toutoune@gmail.com \
    /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).