From: Ingo Molnar <mingo@elte.hu>
Date: Thu, 05 Feb 2009 21:00:18 GMT
Subject: Re: "git revert" feature suggestion: revert the last commit to a file
Message-ID: <20090205210018.GB21500@elte.hu>
In-Reply-To: <7vvdrobobc.fsf@gitster.siamese.dyndns.org>


* Junio C Hamano <gitster@pobox.com> wrote:

> Ingo Molnar <mingo@elte.hu> writes:
> 
> > So i have to do something like:
> >
> >    git revert $(git log -1 --pretty=format:"%h" kernel/softlockup.c)
> >
> > (tucked away in a tip-revert-file helper script.)
> >
> > But it would be so much nicer if i could do the intuitive:
> >
> >    git revert kernel/softlockup.c
> >
> > Or at least, to separate it from revision names cleanly, something like:
> >
> >    git revert -- kernel/softlockup.c
> 
> All three shares one issue.  Does the syntax offer you a way to give
> enough information so that you can confidently say that it will find the
> commit that touched the path most recently?  How is the "most recently"
> defined?
> 
> At least you can restate the first one to:
> 
>     git revert $(git log -1 --pretty=format:"%h" core/softlockup -- kernel/softlockup.c)
> 
> to limit to "the one that touched this file _on this topic_".

All in the current scope of the integration branch, sure. I.e. the same 
scope of commits that "git log kernel/softlockup.c" uses.

	Ingo