public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] repo/gentoo.git, or how committing is challenging
Date: Mon, 14 Dec 2015 12:52:30 -0500	[thread overview]
Message-ID: <CAJ0EP434Z550ebs2kn7G3ur_+jxsuX8LjNaFM_M2unb35Twxug@mail.gmail.com> (raw)
In-Reply-To: <566EA40F.5090806@gentoo.org>

On Mon, Dec 14, 2015 at 6:12 AM, Patrick Lauer <patrick@gentoo.org> wrote:
> Why does the official documentation point me at gkeys-gen, which doesn't
> work

The documentation you linked is a project page for the Gentoo-Keys
project. It represents one possible way to accomplish the goal of
generating a gpg key. It is not the only possible way to get the job
done.

The reference on acceptable keys is GLEP 63, which makes no mention of
gkeys. I would expect you to be able to operate gpg sufficiently well
to generate a key meeting the GLEP specification. If not, you can
always ask for help in a support channel.

>
> On a wiki that's horribly broken

Your definition of "broken" is rather skewed. You are using
non-standard browser addons which block CSS/javascript. It works
perfectly well without such addons.

Shouting loudly "this is broken" does not make it so.


  reply	other threads:[~2015-12-14 17:53 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 [this message]
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
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=CAJ0EP434Z550ebs2kn7G3ur_+jxsuX8LjNaFM_M2unb35Twxug@mail.gmail.com \
    --to=floppym@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