From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SbnaL-0005N3-IN for garchives@archives.gentoo.org; Tue, 05 Jun 2012 06:49:46 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D733BE0732; Tue, 5 Jun 2012 06:49:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id DAEC0E077E for ; Tue, 5 Jun 2012 06:48:51 +0000 (UTC) Received: from pomiocik.lan (p14.ppp.polbox.pl [213.241.7.14]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 397FF1B4023; Tue, 5 Jun 2012 06:48:50 +0000 (UTC) Date: Tue, 5 Jun 2012 08:50:02 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: rich0@gentoo.org Subject: Re: [gentoo-dev] Git braindump: 1 of N: merging & git signing Message-ID: <20120605085002.2bbe9a0d@pomiocik.lan> In-Reply-To: References: <20120604191000.GA3692@localhost> <20120604204132.GB3692@localhost> Organization: Gentoo X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/PtPwijkvEn_fvqPcdszyM7S"; protocol="application/pgp-signature" X-Archives-Salt: 5708bace-c1b6-4de6-9173-9079fbb75b57 X-Archives-Hash: 3b57a4546d5d0737862eaadd8d77339c --Sig_/PtPwijkvEn_fvqPcdszyM7S Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 4 Jun 2012 16:57:42 -0400 Rich Freeman wrote: > If you go back and look at the tree you see a bunch of signed and > unsigned commits. How do you easily detect how the unsigned ones got > there (via a dev with a merge commit, or via other means)? Well, that's not a very good solution but the server-side hooks could also verify the tree state before applying new commits. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/PtPwijkvEn_fvqPcdszyM7S Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAk/NrB4ACgkQfXuS5UK5QB3gLAQAmle/NdX5qpU8M/Xz2VMQEip3 D+XKxc2eSAtsTMSpwyOAc3h3GJBNSRtfM23xDifyWg0GviuwLz+DEJIlXcWTxffS DLGY/CXuXbqcZHMllyV9oXXtwZOZHhPY5mCJskC/jSHeODZw7lMrgMpExjDQmnrE ++ZbQarPErcX2G372Qw= =1Sqk -----END PGP SIGNATURE----- --Sig_/PtPwijkvEn_fvqPcdszyM7S--