From: Junio C Hamano <gitster@pobox.com>
To: Cosmin Apreutesei <cosmin.apreutesei@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: GIT_WORK_TREE and GIT_DIR with git clone
Date: Tue, 21 Jan 2014 12:23:41 -0800 [thread overview]
Message-ID: <xmqq4n4xulrm.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAKJdRamFDDWRZDHBCe7GrXg0OWhLfBPq_ofsvowaW9d8VOGTMA@mail.gmail.com> (Cosmin Apreutesei's message of "Mon, 20 Jan 2014 17:59:16 +0200")
Cosmin Apreutesei <cosmin.apreutesei@gmail.com> writes:
> I would like to be able to tell my users that they can simply do:
>
> git clone --git-dir=_/git/module1/.git module1-url
> git clone --git-dir=_/git/module2/.git module2-url
>
> which will overlay the files from both modules into the current
> directory, which from git's perspective is the work-tree for both
> modules.
Would there be a sensible semantics in the resulting working tree?
Which repository would a new file in such a combined working tree
belong to?
next prev parent reply other threads:[~2014-01-21 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 15:59 GIT_WORK_TREE and GIT_DIR with git clone Cosmin Apreutesei
2014-01-21 20:23 ` Junio C Hamano [this message]
2014-01-21 21:37 ` Cosmin Apreutesei
-- strict thread matches above, loose matches on Subject: below --
2011-03-26 12:58 Kacper Kornet
2011-03-26 19:40 ` Junio C Hamano
2011-03-26 23:37 ` Kacper Kornet
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=xmqq4n4xulrm.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=cosmin.apreutesei@gmail.com \
--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).