Re: git-new-workdir for filesystems without links (e.g. FAT32)?

From: Piotr Krukowiecki <piotr.krukowiecki.news@gmail.com>
Date: Feb 7, 2011, 12:19 UTC
Message-ID: <AANLkTik-P6o954FTH8sUWbnDekT+rcnvk1z8iQ0SXU-i@mail.gmail.com>
In-Reply-To: <20110206191459.GA17939@elie>

On Sun, Feb 6, 2011 at 8:14 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:

Show 11 quoted lines

> Hi Piotr,
>
> Piotr Krukowiecki wrote:
>
>> git-new-workdir requires soft links to work, so obviously it will fail if file
>> system does not support them. Is there any other way for having multiple working
>> dirs with one repository?
>
> I assume you mean a way to share refs between repositories without
> using symlinks?  Then alas, that is not implemented, though there
> is some interest.  See [1] for details.

[...]

> If on the other hand you just want to share objects (not refs) between
> repositories, the GIT_OBJECT_DIRECTORY environment variable might
> help.

I need several working directories (for different branches). I wanted to use git-new-workdir because, as I understand, I could do 'git svn fetch' only once and then 'git rebase' for each working dir. So the only reason was performance (network and disk).

I don't know if sharing objects is enough. If I understand correctly, if a fetch introduces e.g. new branches, then only one working directory will have information about them?

-- 
Piotrek