From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Git Migration: launch plan & schedule (2015/Aug/08-09)
Date: Fri, 03 Jul 2015 17:35:25 -0400 [thread overview]
Message-ID: <5597001D.20002@gentoo.org> (raw)
In-Reply-To: <20150704001941.ed4c1c2aeb9ec2f23086e1d1@gentoo.org>
On 07/03/2015 05:19 PM, Andrew Savchenko wrote:
>
> As I see from git docs only commits and tags may be signed. There
> is no way to sign a push.
This was new to me, but check out the "--signed" flag of git-push (1).
> Moreover there is no need to sign each
> commit, see what Linux says on that:
> http://git.661346.n2.nabble.com/GPG-signing-for-git-commit-td2582986.html
>
> ''
> Btw, there's a final reason, and probably the really real one.
> Signing each commit is totally stupid. It just means that you
> automate it, and you make the signature worth less. It also doesn't
> add any real value, since the way the git DAG-chain of SHA1's work,
> you only ever need _one_ signature to make all the commits
> reachable from that one be effectively covered by that one. So
> signing each commit is simply missing the point.
> ''
I think the next sentence is relevant:
IOW, you don't _ever_ have a reason to sign anything but the "tip".
My interpretation is that it doesn't make sense to sign commits one
through nine if you're going to sign the tenth before pushing. But most
of our commits are small and self-contained so it's probably easier to
automate the signing with repoman than it would be to come up with a
to-sign-or-not-to-sign guide a mile long.
next prev parent reply other threads:[~2015-07-03 21:35 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 21:39 [gentoo-dev] Git Migration: launch plan & schedule (2015/Aug/08-09) Robin H. Johnson
2015-07-02 21:42 ` NP-Hardass
2015-07-03 7:02 ` [gentoo-dev] Celebration subthread: " Duncan
2015-07-03 19:33 ` Jauhien Piatlicki
2015-07-03 1:46 ` [gentoo-dev] " Brian Evans
2015-07-03 6:34 ` Robin H. Johnson
2015-07-03 16:19 ` William Hubbs
2015-07-03 16:24 ` NP-Hardass
2015-07-03 16:41 ` Jason Zaman
2015-07-03 16:35 ` NP-Hardass
2015-07-03 21:19 ` Andrew Savchenko
2015-07-03 21:35 ` Michael Orlitzky [this message]
2015-07-03 21:36 ` Brian Dolbec
2015-07-03 21:40 ` Robin H. Johnson
2015-07-03 23:10 ` Andrew Savchenko
2015-07-04 0:10 ` Rich Freeman
2015-07-03 23:10 ` Rich Freeman
2015-07-03 6:43 ` Justin (jlec)
2015-07-03 7:23 ` Mikle Kolyada
2015-07-03 8:42 ` Daniel Campbell (zlg)
2015-07-03 8:51 ` Igor Savlook
2015-07-03 9:08 ` Justin (jlec)
2015-07-03 9:36 ` Igor Savlook
2015-07-03 12:09 ` Andreas K. Huettel
2015-07-03 13:39 ` Manuel Rüger
2015-08-08 17:47 ` Robin H. Johnson
2015-08-09 5:36 ` [gentoo-dev] Git Migration: go-live! Robin H. Johnson
2015-08-09 7:54 ` Michał Górny
2015-08-09 9:00 ` Michael Weber
2015-08-09 9:31 ` [gentoo-core] " Marc Schiffbauer
2015-08-09 10:02 ` Mike Frysinger
2015-08-09 10:04 ` Francisco Blas Izquierdo Riera (klondike)
2015-08-09 10:16 ` Andrew Savchenko
2015-08-09 21:04 ` Robin H. Johnson
2015-08-09 21:45 ` Andrew Savchenko
2015-08-09 14:56 ` Mike Gilbert
2015-08-09 10:16 ` [gentoo-dev] " Ryan Hill
2015-08-09 10:49 ` Mike Frysinger
2015-08-09 11:22 ` hasufell
2015-08-09 11:55 ` Aaron W. Swenson
2015-08-09 11:56 ` hasufell
2015-08-09 22:40 ` Ryan Hill
2015-08-09 10:18 ` [gentoo-dev] Re: [gentoo-core] " Agostino Sarubbo
2015-08-09 10:46 ` Mike Frysinger
2015-08-09 11:54 ` [gentoo-dev] " Alexey Shvetsov
2015-08-09 12:43 ` [gentoo-scm] " Mike Frysinger
2015-08-09 12:51 ` Alexey Shvetsov
2015-08-09 13:10 ` Rich Freeman
2015-08-09 14:56 ` Robin H. Johnson
2015-08-09 20:03 ` Daniel Campbell (zlg)
2015-08-09 10:50 ` [gentoo-dev] Git Migration: launch plan & schedule (2015/Aug/08-09) Mikle Kolyada
2015-08-23 12:01 ` Andrew Savchenko
2015-08-23 12:28 ` Rich Freeman
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=5597001D.20002@gentoo.org \
--to=mjo@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