Re: Managing multiple branches in git

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 17:24:14
Message-ID: 20090602172414.GE5845@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark Mielke wrote:

> I am curious about why an end user would really care? CVS and SVN both
> kept local workspace directories containing metadata. If anything, I
> find GIT the least intrusive of these three, as the .git is only in the
> top-level directory, whereas CVS and SVN like to pollute every directory.

That's not the problem. The problem is that it is kept in the same
directory as the checked out copy. It would be a lot more usable if it
was possible to store it elsewhere.

Yes, the .svn directories are a PITA.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2009-06-02 17:26:57 Re: Managing multiple branches in git
Previous Message Heikki Linnakangas 2009-06-02 17:18:46 Re: pg_standby -l might destory the archived file