-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 16 Jul 2015 23:06:03 -0400
NP-Hardass wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 07/16/2015 09:25 PM, Brian Dolbec wrote:
> > On Thu, 16 Jul 2015 21:13:09 -0400 NP-Hardass
> > wrote:
> >
> >> -BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/16/2015 09:25 PM, Kent Fredric wrote:
> On 17 July 2015 at 13:13, NP-Hardass
> wrote:
>> Additionally, I feel that a signature is a means of acknowledging
>> that a package has been looked over, and that developer has
>> stated that they appro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/16/2015 09:25 PM, Brian Dolbec wrote:
> On Thu, 16 Jul 2015 21:13:09 -0400 NP-Hardass
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>
>> Not sure if this has been covered in some of the rather long
>> chains of late, but I wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 16 Jul 2015 21:13:09 -0400
NP-Hardass wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Not sure if this has been covered in some of the rather long chains of
> late, but I was thinking about GPG signing, and how the proposed
On 17 July 2015 at 13:13, NP-Hardass wrote:
> Additionally, I feel that a signature is a means of acknowledging that
> a package has been looked over, and that developer has stated that
> they approve of the existing state
That much is somewhat implied by a developer owning a commit. Because
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Not sure if this has been covered in some of the rather long chains of
late, but I was thinking about GPG signing, and how the proposed
workflow requires every developer to sign their commits. Currently,
it's advised that every manifest be signed.
