| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Managing multiple branches in git |
| Date: | 2009-06-02 23:06:14 |
| Message-ID: | 20910.1243983974@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> On Jun 2, 2009, at 3:55 PM, Andrew Dunstan wrote:
>> Running recursive grep on a
>> subversion working copy is quite nasty.
> `git grep` to avoid this issue with Git.
One thing that git does do right is that the .git subdirectory exists
only at the top level of your working directory tree, so it's not too
hard to avoid it in recursive searches. Still, this is one of the
reasons why a separate repository tree would be preferable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2009-06-02 23:08:18 | Re: dblink patches for comment |
| Previous Message | David E. Wheeler | 2009-06-02 23:04:04 | Re: Managing multiple branches in git |