public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: repo/gentoo.git, or how committing is challenging
Date: Mon, 21 Dec 2015 19:45:57 -0500	[thread overview]
Message-ID: <CAGfcS_n1cAdeRay+FQDjZqAMNVh2AP-FS2kz5NVZiFQwOB8gjw@mail.gmail.com> (raw)
In-Reply-To: <20151221185939.13970.qmail@stuge.se>

On Mon, Dec 21, 2015 at 1:59 PM, Peter Stuge <peter@stuge.se> wrote:
> Ryan Hill wrote:
>> You want me to use a potentially unstable live ebuild instead?
>> Well, no, that's not gonna happen.
>
> Are you demanding that someone else produces for you, and refusing to
> do anything but consume?
>

Keep in mind that the GLEP does not require anybody to actually use
gkeys.  It is just a tool intended to make the GLEP easier to follow.

As has been pointed out, we haven't exactly been strict about
enforcing compliance, and for my part I'm not inclined to see a lot
more enforcement until the instructions/tools/etc catch up.  If
anybody wants to see increased adoption of the new GLEP, I'd recommend
focusing more on easy instructions and tools.

That said, anybody who cares enough will figure out how to get it
working.  I just made myself a dedicated tree-signing key and as far
as I could tell the last time I looked at it the key complied.  Just
don't try to send me any encrypted email, since the key in LDAP
probably doesn't work for encryption (having a separate LDAP record
for signing key and communication key might make sense).  :)

--
Rich


  reply	other threads:[~2015-12-22  0:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 17:36 [gentoo-dev] repo/gentoo.git, or how committing is challenging Patrick Lauer
2015-12-13 17:38 ` Patrick Lauer
2015-12-13 18:50   ` Andrew Savchenko
2015-12-13 19:05     ` Patrick Lauer
2015-12-13 19:20 ` Andrew Savchenko
2015-12-13 21:30   ` Mike Gilbert
2015-12-13 21:53     ` Andrew Savchenko
2015-12-14  3:00   ` Brian Dolbec
2015-12-14  6:23     ` Daniel Campbell
2015-12-14 11:12     ` Patrick Lauer
2015-12-14 17:52       ` Mike Gilbert
2015-12-15  0:31       ` Peter Stuge
2015-12-21  3:21     ` [gentoo-dev] " Ryan Hill
2015-12-21 18:59       ` Peter Stuge
2015-12-22  0:45         ` Rich Freeman [this message]
2015-12-22  9:41       ` Patrick Lauer
2015-12-22 12:08         ` Rich Freeman
2015-12-22 12:53           ` Patrick Lauer
2015-12-22 13:14             ` Rich Freeman
2015-12-22 13:31               ` Patrick Lauer
2015-12-22 14:04                 ` Rich Freeman
2015-12-22 18:21                   ` Patrick Lauer
2015-12-22 23:55             ` Peter Stuge

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=CAGfcS_n1cAdeRay+FQDjZqAMNVh2AP-FS2kz5NVZiFQwOB8gjw@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox