Re: Managing multiple branches in git - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Managing multiple branches in git
Date
Msg-id 2d4a65b6d0469ee3dd778f885ac3eb18@biglumber.com
Whole thread Raw
In response to Re: Managing multiple branches in git  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----                              
Hash: RIPEMD160


> Umm, no. there are *no* ,v files in my working copies (I just checked,
> to make sure I wasn't on crack). The repository has them, but the
> working copy does not. SVN does keep the equivalent - that's how you can
> work offline for doing things like 'svn diff'. But it makes the repo
> quite ugly, in fact. Running recursive grep on a subversion working copy
> is quite nasty.

grep -r? No need to use that anymore when a tool like ack is available.
It ignores .svn dirs by default, and basically works the way most
people wish grep worked:

http://betterthangrep.com/

I also agree with Tom Lane elsewhere in this thread that a lot of this is
what may turn out to be pointless wheel spinning: certainly other big
projects (esp. Linux) must have encountered and solved these problems?
Anyone know a kernel hacker / git expert?

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200906021949
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkoluqsACgkQvJuQZxSWSsi0/ACdHQMZeixC5yMYOp0wkqZi/qEE
cqsAnjpjURChqOGOB8vmJ3GjQCm4Ts3n
=4pr9
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Managing multiple branches in git
Next
From: "David E. Wheeler"
Date:
Subject: Re: Managing multiple branches in git