This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: git is live
- From: Steinar Bang <sb at dod dot no>
- To: gdb at sourceware dot org
- Cc: binutils at sourceware dot org
- Date: Sat, 09 Nov 2013 19:28:21 +0100
- Subject: Re: git is live
- Authentication-results: sourceware.org; auth=none
- References: <877gd5iyaz dot fsf at fleche dot redhat dot com> <874n89eidz dot fsf at sandifor-thinkpad dot stglab dot manchester dot uk dot ibm dot com> <CABZhLO_hEnKC3o9LEM5Ej82PnDqy6nOvxXvPcSt8utQ1fPMNmw at mail dot gmail dot com> <87txg9gwmv dot fsf at fleche dot redhat dot com> <5266B987 dot 2000603 at redhat dot com> <87sivt15gw dot fsf at igel dot home>
>>>>> Andreas Schwab <schwab@linux-m68k.org>:
> Pedro Alves <palves@redhat.com> 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.