From: "Frank Ch. Eigler" <fche@elastic.org>
To: Nick Clifton <nickc@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: updatekey command not found
Date: Thu, 06 Apr 2017 10:08:00 -0000 [thread overview]
Message-ID: <20170406100829.GA110882@elastic.org> (raw)
In-Reply-To: <877f2y3s1z.fsf@redhat.com>
Hi, Nick -
> [...] So instead I copied the new key across manually and then
> logged in and added it to my authorized keys. [...]
Those instructions are for that 95% of folks who are limited to a
shell that can only invoke cvs..git and those other "updatekey"
etc. subcommands. You have full shell access, so that doesn't apply
to you. (We don't really advertise this capability, as it's only for
senior maintainers.)
- FChE
prev parent reply other threads:[~2017-04-06 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 7:37 Nick Clifton
2017-04-06 10:08 ` Frank Ch. Eigler [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=20170406100829.GA110882@elastic.org \
--to=fche@elastic.org \
--cc=nickc@redhat.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).