From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | jd(at)commandprompt(dot)com |
Cc: | 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:27:26 |
Message-ID: | 4A04B1CE.7090601@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Joshua,
On 05/09/2009 12:22 AM, Joshua D. Drake wrote:
>> Obviously, an unchecked cvs diff would have produced the same garbage. Any
>> other problems?
> There are a number of conceptual differences. For example as a majority
> svn user, svn diff does not act the way git diff does. In that svn diff
> will only give me the difference within the current working directory.
> It will not go to the beginning of the tree and give me a diff.
git diff .
Although admittedly that takes some time getting used to.
> 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.
git checkout HEAD [--] your_file
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2009-05-08 22:28:50 | Re: strict version of version_stamp.pl |
Previous Message | Alvaro Herrera | 2009-05-08 22:26:20 | Re: strict version of version_stamp.pl |