{"thread":{"id":"26426","subject":"git-new-workdir for filesystems without links (e.g. FAT32)?","startedAt":"2011-02-06T14:20:34Z","lastAt":"2011-02-07T12:19:46Z","messageCount":3,"participants":["Piotr Krukowiecki","Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"160494","messageId":"loom.20110206T151206-851@post.gmane.org","threadId":"26426","inReplyTo":null,"subject":"git-new-workdir for filesystems without links (e.g. FAT32)?","fromName":"Piotr Krukowiecki","fromEmail":"piotr.krukowiecki.news@gmail.com","sentAt":"2011-02-06T14:20:34Z","receivedAt":"2011-02-06T14:20:34Z","isPatch":false,"sender":{"key":"piotr.krukowiecki.news@gmail.com","avatar":null},"body":"Hi, \n\ngit-new-workdir requires soft links to work, so obviously it will fail if file \nsystem does not support them. Is there any other way for having multiple working \ndirs with one repository?\n\nSince git-new-workdir just uses soft links it should be possible to implement it \nnatively in git. Maybe there some patches for this?\n\nI need it because I'm using FAT32 on my dual-boot computer to share data between \nwindows and linux. \n\n\nThanks,\n\n-- \nPiotr Krukowiecki\n"},{"id":"160541","messageId":"20110206191459.GA17939@elie","threadId":"26426","inReplyTo":"loom.20110206T151206-851@post.gmane.org","subject":"Re: git-new-workdir for filesystems without links (e.g. FAT32)?","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-02-06T19:14:59Z","receivedAt":"2011-02-06T19:14:59Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi Piotr,\n\nPiotr Krukowiecki wrote:\n\n> git-new-workdir requires soft links to work, so obviously it will fail if file \n> system does not support them. Is there any other way for having multiple working \n> dirs with one repository?\n\nI assume you mean a way to share refs between repositories without\nusing symlinks?  Then alas, that is not implemented, though there\nis some interest.  See [1] for details.\n\nIt should not be impossible, I think --- something for refs analagous\nto the \".git file\" mechanism might make perfect sense (see\nv1.5.6-rc0~93^2~3, Add platform-independent .git \"symlink\", 2008-02-20\nand \"git log --grep='git file'\" to see development since then).  The\nmain distinction here is that the target of a refs \"symlink\" should\nalso be aware of it, to avoid garbage collecting the shared objects.\n\nIf on the other hand you just want to share objects (not refs) between\nrepositories, the GIT_OBJECT_DIRECTORY environment variable might\nhelp.\n\nGood luck,\nJonathan\n\n[1] http://thread.gmane.org/gmane.comp.version-control.git/150559/focus=150693\n"},{"id":"160603","messageId":"AANLkTik-P6o954FTH8sUWbnDekT+rcnvk1z8iQ0SXU-i@mail.gmail.com","threadId":"26426","inReplyTo":"20110206191459.GA17939@elie","subject":"Re: git-new-workdir for filesystems without links (e.g. FAT32)?","fromName":"Piotr Krukowiecki","fromEmail":"piotr.krukowiecki.news@gmail.com","sentAt":"2011-02-07T12:19:46Z","receivedAt":"2011-02-07T12:19:46Z","isPatch":false,"sender":{"key":"piotr.krukowiecki.news@gmail.com","avatar":null},"body":"On Sun, Feb 6, 2011 at 8:14 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:\n> Hi Piotr,\n>\n> Piotr Krukowiecki wrote:\n>\n>> git-new-workdir requires soft links to work, so obviously it will fail if file\n>> system does not support them. Is there any other way for having multiple working\n>> dirs with one repository?\n>\n> I assume you mean a way to share refs between repositories without\n> using symlinks?  Then alas, that is not implemented, though there\n> is some interest.  See [1] for details.\n[...]\n> If on the other hand you just want to share objects (not refs) between\n> repositories, the GIT_OBJECT_DIRECTORY environment variable might\n> help.\n\nI need several working directories (for different branches). I wanted\nto use git-new-workdir because, as I understand, I could do 'git svn\nfetch' only once and then 'git rebase' for each working dir. So the\nonly reason was performance (network and disk).\n\nI don't know if sharing objects is enough. If I understand correctly,\nif a fetch introduces e.g. new branches, then only one working\ndirectory will have information about them?\n\n\n-- \nPiotrek\n"}]}