Re: [PATCH] commit: teach --gpg-sign option
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 9, 2011, 23:18 UTC
- Message-ID
- <7vmxd9pxd2.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <robbat2-20111009T225253-591026811Z@orbis-terrarum.net>
"Robin H. Johnson" <robbat2@gentoo.org> writes:
> Workflow example: > 1. Dev1 creates a commit, signs it, pushes to central repo. > 2. Dev2 pulls, signs the tip commit, pushes it back.
I personally am not sympathetic to such a "sign every and all commits by multiple people" workflow. If you really want to do such a thing, you can have the second and subsequent one to create a new commit on top whose sole purpose is to hold such a signature (commit --allow-empty --gpg-sig), or use signed tags.