From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Individual developer signing
Date: Thu, 3 Dec 2009 13:51:15 +0100 [thread overview]
Message-ID: <200912031351.20406.bangert@gentoo.org> (raw)
In-Reply-To: <20091203103242.GA6316@veller.net>
[-- Attachment #1: Type: Text/Plain, Size: 368 bytes --]
> BTW: About a third of the Manifests are signed [1].
if we really want to get there, maybe repoman should give a _small_
warning, starting now.
i dont sign my commits and have seen how my commits removed signatures of
others. i am not proud of it - but given that these are apparently never
checked in any way, then no harm is done... or what?
Thilo
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-03 14:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 21:50 [gentoo-dev] Next council meeting on 7 Dec 2009 at 1900UTC Denis Dupeyron
2009-11-26 1:34 ` Brian Harring
2009-11-26 1:39 ` Zac Medico
2009-11-26 15:31 ` Ciaran McCreesh
2009-11-26 16:33 ` Brian Harring
2009-11-26 16:46 ` Ciaran McCreesh
2009-11-27 8:08 ` Brian Harring
2009-11-30 11:30 ` Antoni Grzymala
2009-11-30 11:41 ` Antoni Grzymala
2009-11-30 21:18 ` [gentoo-dev] GPG Infrastructure for Gentoo (Was Council Meeting) Richard Freeman
2009-11-30 22:28 ` Dawid Węgliński
2009-12-01 1:27 ` Robin H. Johnson
2009-12-03 10:32 ` [gentoo-dev] Individual developer signing Torsten Veller
2009-12-03 12:51 ` Thilo Bangert [this message]
2009-12-03 20:35 ` Robin H. Johnson
2009-12-11 16:32 ` [gentoo-dev] " Torsten Veller
2009-12-01 1:08 ` [gentoo-dev] Tree Integrity GLEPS for final review and council approval Robin H. Johnson
2009-11-30 17:57 ` [gentoo-dev] Next council meeting on 7 Dec 2009 at 1900UTC Thomas Sachau
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=200912031351.20406.bangert@gentoo.org \
--to=bangert@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