git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Piotr Krukowiecki <piotr.krukowiecki.news@gmail.com>
Cc: git@vger.kernel.org, Pierre Habouzit <madcoder@debian.org>
Subject: Re: git-new-workdir for filesystems without links (e.g. FAT32)?
Date: Sun, 6 Feb 2011 13:14:59 -0600	[thread overview]
Message-ID: <20110206191459.GA17939@elie> (raw)
In-Reply-To: <loom.20110206T151206-851@post.gmane.org>

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.

It should not be impossible, I think --- something for refs analagous
to the ".git file" mechanism might make perfect sense (see
v1.5.6-rc0~93^2~3, Add platform-independent .git "symlink", 2008-02-20
and "git log --grep='git file'" to see development since then).  The
main distinction here is that the target of a refs "symlink" should
also be aware of it, to avoid garbage collecting the shared objects.

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

Good luck,
Jonathan

[1] http://thread.gmane.org/gmane.comp.version-control.git/150559/focus=150693

  reply	other threads:[~2011-02-06 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 14:20 git-new-workdir for filesystems without links (e.g. FAT32)? Piotr Krukowiecki
2011-02-06 19:14 ` Jonathan Nieder [this message]
2011-02-07 12:19   ` Piotr Krukowiecki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110206191459.GA17939@elie \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=madcoder@debian.org \
    --cc=piotr.krukowiecki.news@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).