From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19040 invoked by alias); 9 Nov 2013 18:28:46 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 19031 invoked by uid 89); 9 Nov 2013 18:28:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: plane.gmane.org Received: from Unknown (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Sat, 09 Nov 2013 18:28:43 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VfDGr-0006gw-Ke for gdb@sourceware.org; Sat, 09 Nov 2013 19:28:33 +0100 Received: from cm-84.208.248.210.getinternet.no ([84.208.248.210]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Nov 2013 19:28:33 +0100 Received: from sb by cm-84.208.248.210.getinternet.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Nov 2013 19:28:33 +0100 Mail-Followup-To: gdb@sourceware.org To: gdb@sourceware.org From: Steinar Bang Subject: Re: git is live Date: Sat, 09 Nov 2013 18:28:00 -0000 Message-ID: References: <877gd5iyaz.fsf@fleche.redhat.com> <874n89eidz.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com> <87txg9gwmv.fsf@fleche.redhat.com> <5266B987.2000603@redhat.com> <87sivt15gw.fsf@igel.home> Mime-Version: 1.0 Content-Type: text/plain Mail-Copies-To: never User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (windows-nt) Cc: binutils@sourceware.org X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00033.txt.bz2 >>>>> Andreas Schwab : > Pedro Alves writes: >> Yeah. Oh well, not a show stopper. Maybe I'll find a way to tell >> git to treat a range of commits as a single commit for blame/log >> purposes, so that "git blame" punches through that hole. > You can do that with grafts or replace objects (which can change your > view of the commit graph by pretending that a commit has a different > parent). A blog article on git replace here (by the "Pro git" author): http://git-scm.com/blog/2010/03/17/replace.html In short: in a "git rewrite", there will be a file created, that has the sha1 of the original commit as its name, and the sha1 of a new commit that should be used instead, as its content.