Re: Re: Re: fsck --full is Ok, but clones are not, "missing commits"?!

From: Dmitry Potapov <dpotapov@gmail.com>
Date: Apr 16, 2008, 16:23 UTC
Message-ID: <20080416162338.GD3133@dpotapov.dyndns.org>
In-Reply-To: <20080416145900.GA10777@machine.or.cz>

On Wed, Apr 16, 2008 at 04:59:00PM +0200, Petr Baudis wrote:

Show 5 quoted lines

> On Wed, Apr 16, 2008 at 04:14:24PM +0400, Dmitry Potapov wrote:
> > info/grafts should never be used during normal work.
> 
> I don't really agree with this advice in general. Grafts can be very
> useful especially when migrating to Git

I agree that they can be very useful in the process of migrating, but I would not recommend to leave them _after_ the migration process is complete.

> The _BAD_ grafts are those that replace list of commit's parents instead
> of just appending (typically to an empty one). I didn't actually have
> any idea people use grafts in such a twisted and perverse way... ;-)

They are used to replace _BAD_ commits imported from CVS. History in CVS can be very strange and even with best conversation tools, you may end up with something not exactly what you want. So, you want to replace some commits with corrected versions of them. So, you add those commits to Git repo, "fix" history, and then using gitk check that now you have exactly what you want. If now the history is okay then you can use git filter-branch to make those changes real.

Dmitry