From: Junio C Hamano <junkio@cox.net>
To: apw@us.ibm.com (Amos Waterland)
Cc: git@vger.kernel.org
Subject: Re: Subproject clones
Date: Fri, 11 May 2007 18:32:41 -0700 [thread overview]
Message-ID: <7vmz0a7rnq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vr6pm7ry4.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 11 May 2007 18:26:27 -0700")
Junio C Hamano <junkio@cox.net> writes:
> apw@us.ibm.com (Amos Waterland) writes:
>
>> Is this intentional? Shouldn't clone get the entire superproject?
>
> Yes. As 1.5.2 draft release notes and my response to somebody
> else last night mentioned, the plumbing level subproject support
> does _NOT_ recurse into subproject and this is deliberate.
Namely:
http://article.gmane.org/gmane.comp.version-control.git/46934
http://article.gmane.org/gmane.comp.version-control.git/46940
next prev parent reply other threads:[~2007-05-12 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 1:16 Subproject clones Amos Waterland
2007-05-12 1:26 ` Junio C Hamano
2007-05-12 1:32 ` Junio C Hamano [this message]
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=7vmz0a7rnq.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=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).