From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Raible Subject: Re: Re: [PATCH] Docs: git checkout --orphan: `root commit' and `branch head' Date: Tue, 27 Sep 2011 13:34:33 -0700 Message-ID: <4E823359.7080602@nextest.com> References: <1316960136073-6829212.post@n2.nabble.com> <1316961212.4388.5.camel@centaur.lab.cmartin.tk> <7vaa9r2jii.fsf@alter.siamese.dyndns.org> <1317073309.5579.9.camel@centaur.lab.cmartin.tk> <4E81F080.7010905@drmicha.warpmail.net> <7v39fhyk21.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Michael Witten , Michael J Gruber , =?UTF-8?B?Q2FybG9zIE1hcnTDrW4gTmlldG8=?= , vra5107 , To: Junio C Hamano X-From: git-owner@vger.kernel.org Tue Sep 27 22:39:59 2011 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R8eRX-0003Xs-Qv for gcvg-git-2@lo.gmane.org; Tue, 27 Sep 2011 22:39:56 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753777Ab1I0Ujq (ORCPT ); Tue, 27 Sep 2011 16:39:46 -0400 Received: from smtps.nextest.com ([12.96.234.114]:55992 "EHLO exchange.DOMAIN1.nextest.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753771Ab1I0Ujp (ORCPT ); Tue, 27 Sep 2011 16:39:45 -0400 X-Greylist: delayed 311 seconds by postgrey-1.27 at vger.kernel.org; Tue, 27 Sep 2011 16:39:45 EDT Received: from [131.101.151.13] (131.101.151.13) by Exchange.DOMAIN1.nextest.com (131.101.21.39) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 27 Sep 2011 13:34:33 -0700 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 In-Reply-To: <7v39fhyk21.fsf@alter.siamese.dyndns.org> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On 11:59 AM, Junio C Hamano wrote: > Michael Witten writes: > >> It seems like a more logical approach would be instead for "git >> commit" to take a "--root" option that would create a new root commit >> based on the current index and then point the current branch head to >> the new root commit. Thus: >> >> $ git checkout -b new_branch old_branch >> $ # Manipulate or not >> $ git commit --root >> >> That's how people think. Not this person. I like the idea but I'd rather see: git commit --no-parent "parent" at least appears in gitk and therefore newcomers will prob have a better chance of understanding the intent w/out needing to otherwise unnecessary terminology.