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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Feb 6, 2011 at 8:14 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote:
> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]