From: Drak <drak@zikula•org>
To: System undo crew <unsystem@lists•dyne.org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Amir Taaki <genjix@riseup•net>
Subject: Re: [Bitcoin-development] [unSYSTEM] DarkWallet Best Practices
Date: Thu, 19 Dec 2013 16:32:10 +0000 [thread overview]
Message-ID: <CANAnSg312feKyW-LtRu+n99ODn4KDTja__Wp7bRz+k=5ox3yHg@mail.gmail.com> (raw)
In-Reply-To: <538d3c4677a4332ae8341e37d1a77d5e.squirrel@fruiteater.riseup.net>
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
On 19 December 2013 16:04, Amir Taaki <genjix@riseup•net> wrote:
> About signing each commit, Linus advises against it:
>
> http://git.661346.n2.nabble.com/GPG-signing-for-git-commit-td2582986.html
Yeah, it makes no sense after reading it. Nice catch.
However, his recommendation for signing tags with `git tag -s` should
probably be incorporated into the spec as a MUST.
Drak
[-- Attachment #2: Type: text/html, Size: 887 bytes --]
next prev parent reply other threads:[~2013-12-19 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 13:17 [Bitcoin-development] " Peter Todd
2013-12-19 15:46 ` Drak
[not found] ` <dde469d7ce77a748fb4c279334deb643.squirrel@fruiteater.riseup.net>
[not found] ` <538d3c4677a4332ae8341e37d1a77d5e.squirrel@fruiteater.riseup.net>
2013-12-19 16:32 ` Drak [this message]
2013-12-19 17:23 ` [Bitcoin-development] [unSYSTEM] " Mike Belshe
2013-12-19 17:44 ` [Bitcoin-development] " Peter Todd
2013-12-19 18:05 ` [Bitcoin-development] [unSYSTEM] " Drak
2013-12-20 6:52 ` [Bitcoin-development] " Wendell
[not found] ` <52B359C4.3050106@sindominio.net>
2013-12-20 17:32 ` [Bitcoin-development] [unSYSTEM] " Taylor Gerring
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='CANAnSg312feKyW-LtRu+n99ODn4KDTja__Wp7bRz+k=5ox3yHg@mail.gmail.com' \
--to=drak@zikula$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=genjix@riseup$(echo .)net \
--cc=unsystem@lists$(echo .)dyne.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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