| From: | Marko Kreen <markokr(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Mark Mielke <mark(at)mark(dot)mielke(dot)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:26:57 |
| Message-ID: | e51f66da0906021026h2920af85vbd27a848d044b2dc@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/2/09, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> 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.
export GIT_DIR=...
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-06-02 17:37:01 | Re: Managing multiple branches in git |
| Previous Message | Alvaro Herrera | 2009-06-02 17:24:14 | Re: Managing multiple branches in git |