public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Gentoo GPG key policies
Date: Thu, 14 Mar 2013 09:30:19 -0700	[thread overview]
Message-ID: <5141FB1B.1090004@gentoo.org> (raw)
In-Reply-To: <20130314171415.525323a2@pomiocik.lan>

On 03/14/2013 09:14 AM, Michał Górny wrote:
> On Thu, 14 Mar 2013 08:26:04 -0700
> Zac Medico <zmedico@gentoo.org> wrote:
> 
>> On 03/14/2013 02:12 AM, Robin H. Johnson wrote:
>>>> But my first attempt to do a signed commit has failed:
>>> Your GPG agent is broken/missing.
>>>
>>> zmedico/portage-dev: 
>>> Maybe a good idea to check for agent sanity before trying to use it?
>>
>> Yeah, we could have it do a test signature to verify that it's working
>> properly before it tries to commit anything. We've got this bug filed:
>>
>>   https://bugs.gentoo.org/show_bug.cgi?id=298605
> 
> If that means doing an additional signature every time something is
> going to be committed, that sounds like an overkill. If we were to do
> something radical, I'd rather be in favor of disabling keyword
> expansion completely and finally being able to do sane commits. 

We could do that if we simply add all files using the cvs -kb option.
However, Fabian has requested that we keep the keywords for the purposes
of his prefix tree merging script:

http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg55238.html
-- 
Thanks,
Zac


  reply	other threads:[~2013-03-14 16:30 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 23:27 [gentoo-dev] RFC: Gentoo GPG key policies Robin H. Johnson
2013-02-18 23:41 ` Robin H. Johnson
2013-02-19  3:36   ` Kent Fredric
2013-02-19  4:09     ` Robin H. Johnson
2013-02-19  4:46       ` Brian Dolbec
2013-02-19  7:38       ` Kent Fredric
2013-02-19 15:52         ` Alec Warner
2013-02-19  4:25     ` [gentoo-dev] " Ryan Hill
2013-02-19  6:51 ` [gentoo-dev] " Eray Aslan
2013-02-20  0:34 ` Stefan Behte
2013-02-20  3:12   ` Robin H. Johnson
2013-02-20  6:32     ` Alec Warner
2013-02-20 17:05       ` Robin H. Johnson
2013-02-20 18:41 ` James Cloos
2013-02-20 19:36   ` Robin H. Johnson
2013-02-20 20:22     ` Andreas K. Huettel
2013-02-20 21:31       ` Robin H. Johnson
2013-02-20 20:38 ` Luis Ressel
2013-02-20 21:37   ` Robin H. Johnson
2013-02-20 21:55     ` Luis Ressel
2013-02-21  9:09 ` Michał Górny
2013-02-21  9:41   ` Markos Chandras
2013-02-26 10:10 ` grozin
2013-02-27 15:12   ` Luis Ressel
2013-02-27 19:04     ` Robin H. Johnson
2013-02-27 20:27       ` Alec Warner
2013-03-14  3:50       ` grozin
2013-03-14  7:19         ` justin
2013-03-14  9:12         ` Robin H. Johnson
2013-03-14 15:26           ` Zac Medico
2013-03-14 16:14             ` Michał Górny
2013-03-14 16:30               ` Zac Medico [this message]
2013-03-15  0:58                 ` Robin H. Johnson
2013-03-15  1:01               ` Robin H. Johnson
2013-03-15  2:32                 ` Michael Mol
2013-03-15  3:18                   ` Robin H. Johnson
2013-03-15  3:33                     ` Michael Mol
2013-03-15  5:12                       ` Robin H. Johnson
2013-03-15  4:44                     ` Michał Górny
2013-03-15  5:01                       ` Robin H. Johnson
2013-03-22  6:37           ` grozin
2013-03-22  8:36             ` Panagiotis Christopoulos
2013-03-22  8:47               ` grozin
2013-03-22 14:19                 ` David Abbott

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=5141FB1B.1090004@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@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