From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Managing multiple branches in git |
Date: | 2009-06-02 16:32:09 |
Message-ID: | 4A255409.70201@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/02/2009 05:43 PM, Tom Lane wrote:
> Marko Kreen<markokr(at)gmail(dot)com> writes:
>> They cannot be same commits in GIT as the resulting tree is different.
> I don't see any even-approximately-sane way to handle similar cases
> in git. From what I've learned so far, you can have one checkout
> at a time in a git working tree, which would mean N copies of the
> entire repository if I want N working trees. Not to mention the
> impossibility of getting it to regard parallel commits as related
> in any way whatsoever.
You can use the "--reference" option to git clone to refer to objects in
another clone. That way most of the commits will only be stored in there
- only the local commits will be in the local checkout.
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-02 16:33:51 | Re: Managing multiple branches in git |
Previous Message | Marko Kreen | 2009-06-02 16:31:30 | Re: Managing multiple branches in git |