Re: GIT - breaking backward compatibility

From: Petr Baudis <pasky@suse.cz>
Date: Sep 20, 2005, 07:29 UTC
Message-ID: <20050920072928.GA17621@pasky.or.cz>
In-Reply-To: <432F92FC.4000405@didntduck.org>

Dear diary, on Tue, Sep 20, 2005 at 06:41:32AM CEST, I got a letter where Brian Gerst <bgerst@didntduck.org> told me that...

Show 26 quoted lines

> Linus Torvalds wrote:
> >
> >On Tue, 20 Sep 2005, Brian Gerst wrote:
> >
> >>Essentially what I want to do is:
> >>
> >>git-ls-files --others | xargs git-update-index --add --
> >>git-ls-files --deleted | xargs git-update-index --remove --
> >>git-ls-files --modified | xargs git-update-index --
> >>
> >>This will completely resync the index and cache to the working tree 
> >>state after applying a patch.
> >
> >
> >It will also be extremely inefficient.
> >
> >If you really have a _patch_, then "git-apply --index" is what you want to 
> >apply it with. It applies a patch _and_ updates the index as appropriate. 
> >It's how git-applymbox can apply hundreds of patches in short order.
> >
> >		Linus
> >
> 
> That would be great, if git-apply accepted fuzzy patches.  I am trying 
> to apply the -mm series patches, which often are slightly out of date. 
> Andrew doesn't rebase them until they won't apply at all.

cg-patch will process fuzzy patches and update the cache properly. It doesn't handle rename/copy patches yet, though.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.