From: Petr Baudis <pasky@suse.cz>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: GIT - breaking backward compatibility
Date: Tue, 20 Sep 2005 09:29:28 +0200 [thread overview]
Message-ID: <20050920072928.GA17621@pasky.or.cz> (raw)
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...
> 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.
next prev parent reply other threads:[~2005-09-20 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 2:07 GIT - breaking backward compatibility Junio C Hamano
2005-09-20 4:12 ` Brian Gerst
2005-09-20 4:33 ` Linus Torvalds
2005-09-20 4:41 ` Brian Gerst
2005-09-20 5:03 ` Linus Torvalds
2005-09-20 7:29 ` Petr Baudis [this message]
2005-09-20 6:19 ` Junio C Hamano
2005-09-20 13:08 ` Petr Baudis
[not found] ` <20050920062549.GI15165MdfPADPa@greensroom.kotnet.org>
[not found] ` <7v3bo06xv4.fsf@assigned-by-dhcp.cox.net>
2005-09-20 7:11 ` Sven Verdoolaege
2005-09-20 13:23 ` Petr Baudis
2005-09-22 14:41 ` Petr Baudis
2005-09-23 6:02 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050920072928.GA17621@pasky.or.cz \
--to=pasky@suse.cz \
--cc=bgerst@didntduck.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).