From: Enrico Weigelt <weigelt@metux.de>
To: git <git@vger.kernel.org>
Subject: Re: GIT & Symbolic Links
Date: Sat, 17 Mar 2012 17:00:15 +0100 [thread overview]
Message-ID: <20120317160015.GB18712@mailgate.onlinehome-server.info> (raw)
In-Reply-To: <CACHQFzEJATc2hiSdAgoGg3vssQ-CShF+89TOkzVwaf_ujYy+3w@mail.gmail.com>
* Sassy Natan <sassyn@gmail.com> wrote:
Hi,
> So for the example let's consider that user A clone the DEV GIT Repo
> into his/her home folder (/home/A/DEV)
> User B want to clone the same Repo. But now, I don't want user B to
> clone the all tree and files, but instead to have a symbolic links to
> the /home/A/DEV folder.
> All files and directories in the /home/B/DEV will be a links to the /home/A/DEV.
Symlinks wont fit here, as the userland sees them as links (and treats
them as such). What you're looking for is some solution that does the cow
stuff hidden from the normal userland. Perhaps via unionfs or something
fuse-based.
BUT: I'd first raise the question if your tree needs to be that big
at all. Perhaps it should be splitted into several smaller ones.
What actually does your tree make that big ?
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next prev parent reply other threads:[~2012-03-17 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACHQFzEqe-SwpCgjgGRDdzcUQW_+8-TdLsRV6KbKorvq7dJi+g@mail.gmail.com>
2012-03-12 16:44 ` GIT & Symbolic Links Sassy Natan
2012-03-13 10:06 ` Kevin
2012-03-17 16:00 ` Enrico Weigelt [this message]
2012-03-17 17:05 ` Andrew Sayers
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=20120317160015.GB18712@mailgate.onlinehome-server.info \
--to=weigelt@metux.de \
--cc=git@vger.kernel.org \
/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).