From: apw@us.ibm.com (Amos Waterland)
To: git@vger.kernel.org
Subject: Subproject clones
Date: Fri, 11 May 2007 21:16:00 -0400 [thread overview]
Message-ID: <20070512011600.GA24354@us.ibm.com> (raw)
The logic in t3040-subprojects-basic.sh assumes that comparing the
output of 'git-ls-files -s' when run in the original superproject and
when run in the cloned superproject is a good test that cloning worked.
However, the output of git-ls-files does not include the files in
subprojects, so this test passes, even though the clone contains only
the directories of the subprojects and none of their containing files
or .git subdirectories.
In other words, given this:
superproject
sub1
Makefile
sub2
Makefile
when somebody does `git-clone superproject', I believe they expect to
get the same tree. Instead, they get this:
superproject
sub1
sub2
Note that `git-clone superproject/sub1` works as expected, but this
sequence fails:
git-clone superproject foo
cd foo
git-clone ../superproject/sub1
As does this sequence:
git-clone superproject foo
cd foo/sub1
git-pull ../superproject/sub1
So there is no way that I can see to actually clone a project that has
subprojects.
Is this intentional? Shouldn't clone get the entire superproject?
next reply other threads:[~2007-05-12 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 1:16 Amos Waterland [this message]
2007-05-12 1:26 ` Subproject clones Junio C Hamano
2007-05-12 1:32 ` Junio C Hamano
2007-05-12 8:05 ` Sven Verdoolaege
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=20070512011600.GA24354@us.ibm.com \
--to=apw@us.ibm.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).