From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] please sign your manifests
Date: Tue, 12 Feb 2013 15:14:15 -0600 [thread overview]
Message-ID: <20130212211415.GA4364@linux1> (raw)
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
All,
as preparation for the up-coming cvs->git migration of the portage tree,
the council is strongly suggesting that from this point forward all developers
sign their manifests with their gpg key as described in the developer's
manual [1].
If you have any questions on this, please feel free to let us know.
On behalf of the council,
William
[1] http://devmanual.gentoo.org/general-concepts/manifest/index.html
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2013-02-12 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130212211415.GA4364@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev-announce@lists.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