From: Sven Verdoolaege <skimo@kotnet.org>
To: Amos Waterland <apw@us.ibm.com>
Cc: git@vger.kernel.org
Subject: Re: Subproject clones
Date: Sat, 12 May 2007 10:05:15 +0200 [thread overview]
Message-ID: <20070512080515.GH942MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <20070512011600.GA24354@us.ibm.com>
On Fri, May 11, 2007 at 09:16:00PM -0400, Amos Waterland wrote:
> 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:
I'm working on something like that.
See the thread at
http://article.gmane.org/gmane.comp.version-control.git/46163
I hope to send out an updated version later this weekend.
skimo
prev parent reply other threads:[~2007-05-12 8:05 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
2007-05-12 8:05 ` Sven Verdoolaege [this message]
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=20070512080515.GH942MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=apw@us.ibm.com \
--cc=git@vger.kernel.org \
--cc=skimo@liacs.nl \
/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).