From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: strict version of version_stamp.pl |
Date: | 2009-05-08 22:41:20 |
Message-ID: | 20090508224120.GO10794@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund wrote:
> Hi Alvaro,
>
> On 05/09/2009 12:26 AM, Alvaro Herrera wrote:
>>> Perhaps a more difficult problem is that there is no easy way to update
>>> a single file within a git repo. In cvs or svn, if I blow something up
>>> on a particular file and I just want to take a fresh look, I just rm;svn
>>> update.
>> Hmm, you should use "git revert" for that (same with SVN actually).
> Uh. Unfortunately not. git revert is for reverting the effects of an
> earlier commit, not a working copy difference.
Thanks for the clarification :-)
So how do you revert WC changes? At least I got the SVN part right --
which is not surprising because that's the one I actually use. Oh, and
monotone uses 'revert' for the WC meaning too (the other one does not
really make much sense to me, but so does git as a whole)
(You can't be serious that for reverting a WC file to the repository
state you use "git checkout"?)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-05-08 23:00:58 | Re: strict version of version_stamp.pl |
Previous Message | Andres Freund | 2009-05-08 22:28:50 | Re: strict version of version_stamp.pl |