From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Ulrich Drepper via Gcc <gcc@gcc.gnu.org>
Subject: Re: commit signing
Date: Wed, 14 Sep 2022 10:15:46 +0100 [thread overview]
Message-ID: <CAH6eHdRP8iXzLuwdpetwG7kw--rxPOiYg9X+eEp+wswxHgvN9w@mail.gmail.com> (raw)
In-Reply-To: <CAP3s5k_KxtoHcEff7B=m9ew1w4YZZg6o4_1EhyjT0dc0_B9USA@mail.gmail.com>
On Wed, 14 Sept 2022 at 10:12, Ulrich Drepper wrote:
> The key creation ideally is a one-time effort. The git configuration is
> for everyone using the gcc git tree a once-per-local-repository effort (and
> can be scripted, the gcc repo could even contain a script for that).
No opinion yet on the rest of the email, but we already have a script
to set up a git tree for gcc work, so that would be the natural place
to add this:
https://gcc.gnu.org/gitwrite.html#vendor
next prev parent reply other threads:[~2022-09-14 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 9:11 Ulrich Drepper
2022-09-14 9:15 ` Jonathan Wakely [this message]
2022-09-14 11:31 ` Richard Biener
2022-09-14 12:07 ` Jakub Jelinek
2022-09-14 12:07 ` Ulrich Drepper
2022-09-28 17:03 ` Ulrich Drepper
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=CAH6eHdRP8iXzLuwdpetwG7kw--rxPOiYg9X+eEp+wswxHgvN9w@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=drepper@redhat.com \
--cc=gcc@gcc.gnu.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).