From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Git Migration: launch plan & schedule (2015/Aug/08-09)
Date: Sat, 4 Jul 2015 00:19:41 +0300 [thread overview]
Message-ID: <20150704001941.ed4c1c2aeb9ec2f23086e1d1@gentoo.org> (raw)
In-Reply-To: <20150703161913.GA1379@linux1>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
Hi,
On Fri, 3 Jul 2015 11:19:13 -0500 William Hubbs wrote:
> On Fri, Jul 03, 2015 at 06:34:41AM +0000, Robin H. Johnson wrote:
> > On Thu, Jul 02, 2015 at 09:46:18PM -0400, Brian Evans wrote:
> > > Does this mean that https://wiki.gentoo.org/wiki/Gentoo_git_workflow
> > > is no longer draft or needs work or another document is meant to
> > > display the new flow?
> > It does cover most of the things needed.
> >
> > It could use some revision regarding gkeys, and I'd like to also mandate
> > signed pushes in addition to signed commits.
>
> A push doesn't create any data, it just uploads it to the repo, so how
> do you sign a push?
As I see from git docs only commits and tags may be signed. There
is no way to sign a push. 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.
''
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-07-03 21:20 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 [this message]
2015-07-03 21:35 ` Michael Orlitzky
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=20150704001941.ed4c1c2aeb9ec2f23086e1d1@gentoo.org \
--to=bircoph@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