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 1SaCal-0005E9-3F for garchives@archives.gentoo.org; Thu, 31 May 2012 21:07:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C72D1E068F; Thu, 31 May 2012 21:07:21 +0000 (UTC) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.213.181]) by pigeon.gentoo.org (Postfix) with ESMTP id EE2CAE04E7 for ; Thu, 31 May 2012 21:06:35 +0000 (UTC) Received: by yenl3 with SMTP id l3so1364806yen.40 for ; Thu, 31 May 2012 14:06:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=IUP+MT8UdWpbyvgMLXzXrWJjucfeidlTnCFmnUDIn+0=; b=QY4LSF8SUIuJqX2kKc1ofxO0fLeg14ECJFbVzDapByVPSX71e3SrOxGaMBEwhogGOu DWcwtd+Odttsf4TFckVwce2P8PxzTQItUisy2UvIr7Dk8qgUJihMvrhiNBuEUPZuWm2X y+oidQZsdna9bDkLimw1wWM1u7IsEZv/SgJnMLqrTvbDjS5XvVRKBGVa4mjYKKfLfx+N dI6Cy/LSI8itDjBdK0PljHKWgwHcml/FvFwieMOFRjurr1RQ2dM338QGjuF8W442V+aF xMieByL+xaGnugTbGIo7PNkRgZv69k96FHRMk4jGvEUJKcfEik4WzkvnhTBSmoKSZ/4a LNMA== Received: by 10.60.27.6 with SMTP id p6mr168272oeg.37.1338498395366; Thu, 31 May 2012 14:06:35 -0700 (PDT) Received: from linux1 (cpe-76-187-77-158.tx.res.rr.com. [76.187.77.158]) by mx.google.com with ESMTPS id rr9sm3367396obc.8.2012.05.31.14.06.33 (version=SSLv3 cipher=OTHER); Thu, 31 May 2012 14:06:34 -0700 (PDT) Sender: William Hubbs Received: by linux1 (sSMTP sendmail emulation); Thu, 31 May 2012 16:06:33 -0500 Date: Thu, 31 May 2012 16:06:33 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Portage Git migration - clean cut or git-cvsserver Message-ID: <20120531210633.GB25021@linux1> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20120531191804.GA24784@linux1> <20120531213303.57529c85@pomiocik.lan> 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-sha1; protocol="application/pgp-signature"; boundary="1LKvkjL3sHcu1TtY" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: a9b4513d-fe28-4ad8-888b-a4f3799d44b9 X-Archives-Hash: 0a383617a38209af0d6d2af489b3e9f0 --1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 31, 2012 at 03:58:43PM -0400, Rich Freeman wrote: > On Thu, May 31, 2012 at 3:33 PM, Micha=C5=82 G=C3=B3rny wrote: > > What would git signing work with rebased commits? Would all of them > > have to be signed once again? > > >=20 > The whole point of rebasing is to throw away history (which is either > good or bad based on your perspective). >=20 > So, if 14 devs spend 3 years and 2000 commits working on something in > a branch, and I commit it to master using a rebase, then all you'll > see in the master history is that rich0 committed 20k lines of code to > master on May 31st, and that would be signed by me. You don't commit to master with a rebase,; it is always a merge. The type of merge is what controls what you see in the logs. If you rebase your branch on master, merge to master then run "git pull --rebase" then push, you will get a fast forward merge, which shows the individual commits. If you don't include the rebasing, you get another type of merge which just shows up in the logs as one commit afaik. William --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk/H3VkACgkQblQW9DDEZTjoawCeI5qfwNSbKkzI6rf4g2r2rRuF CEsAoK5ITSPyjmT/tIIf1tDvCB3ARV9f =0K8t -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY--