| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Mark Mielke <mark(at)mark(dot)mielke(dot)cc> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Managing multiple branches in git |
| Date: | 2009-06-02 19:38:23 |
| Message-ID: | 20090602193823.GF5845@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mark Mielke wrote:
> I just don't understand why you care. If the CVS directories didn't bug
> you before, why does the single .git directory bug you now? I'm
> genuinely interested as I don't get it. :-)
It doesn't. What bugs me is that the database (the "pulled" tree if you
will) is stored in it. It has already been pointed out how to put it
elsewhere, so no need to explain that.
What *really* bugs me is that it's so difficult to have one "pulled"
tree and create a bunch of checked out copies from that.
(In the CVS world, I kept a single rsync'ed copy of the anoncvs
repository, and I could do multiple "cvs checkout" copies from there
using different branches.)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Mielke | 2009-06-02 19:55:31 | Re: Managing multiple branches in git |
| Previous Message | Mark Mielke | 2009-06-02 19:17:01 | Re: Managing multiple branches in git |