Re: strict version of version_stamp.pl
От | Robert Haas |
---|---|
Тема | Re: strict version of version_stamp.pl |
Дата | |
Msg-id | 603c8f070905081705y41fad1feoa8cc20dcc7557ff8@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: strict version of version_stamp.pl (Alvaro Herrera <alvherre@commandprompt.com>) |
Список | pgsql-hackers |
On Fri, May 8, 2009 at 6:41 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote: > 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"?) Yes, that's right. I found that a bit odd too, but it's really not bad once you get used to it. If you want to blow away ALL your changes, you can use "git reset --hard". If you want to remove all the untracked files from your working tree, you can use "git clean". ...Robert
В списке pgsql-hackers по дате отправления: