From: Sven Verdoolaege <skimo@kotnet.org>
To: Eran Tromer <git2eran@tromer.org>
Cc: Alex Riesen <raa.lkml@gmail.com>,
VMiklos <vmiklos@frugalware.org>,
git@vger.kernel.org
Subject: Re: question about git-submodule
Date: Sun, 05 Aug 2007 16:59:22 +0200 [thread overview]
Message-ID: <20070805145922.GC999MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <46B3B3D2.6030000@tromer.org>
On Fri, Aug 03, 2007 at 07:01:38PM -0400, Eran Tromer wrote:
> $ mkdir super
> $ cd super
> $ git init
> $ git submodule add ../sub-to-be sub
You probably don't want to do this as this URL
probably won't work for anyone who wants to clone
your superproject.
> BTW, is there any easy way to create a submodule directly inside the
> supermodule's working tree, instead of cloning it as in the above example?
Do you want to use the submodule porcelain or just the plumbing?
If you simply want to add a submodule locally, "git add" will do that for
you just fine. It's only when you want to make it easier for people who
clone your superproject to get updates of the submodules that you
should set up the information required by "git submodule" in .gitmodules
(see end of module_add in git-submodule.sh).
Note that the "url" can be set directly in your git config
(without specifying it in .gitmodules), but then anyone who clones
from you will have to modify his config "manually" too.
For some reason, the "path" element is required, even if it is equal
to the submodule name.
skimo
next prev parent reply other threads:[~2007-08-05 14:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 21:46 question about git-submodule VMiklos
2007-07-15 8:39 ` Sven Verdoolaege
2007-07-15 10:47 ` Alex Riesen
2007-07-15 10:54 ` VMiklos
2007-07-15 13:50 ` Alex Riesen
2007-07-15 13:54 ` VMiklos
2007-07-15 14:02 ` Sven Verdoolaege
2007-07-15 14:26 ` VMiklos
2007-07-15 14:48 ` Sven Verdoolaege
2007-07-15 15:05 ` VMiklos
2007-07-15 15:21 ` Sven Verdoolaege
2007-07-15 15:40 ` VMiklos
2007-07-15 21:45 ` Sven Verdoolaege
2007-07-15 22:29 ` VMiklos
2007-07-16 10:39 ` Sven Verdoolaege
2007-07-16 11:07 ` VMiklos
2007-07-15 11:51 ` Sven Verdoolaege
2007-07-15 13:42 ` Alex Riesen
2007-07-15 13:52 ` Sven Verdoolaege
2007-08-03 23:01 ` Eran Tromer
2007-08-05 14:59 ` Sven Verdoolaege [this message]
2007-08-06 17:23 ` Eran Tromer
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=20070805145922.GC999MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=git2eran@tromer.org \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=skimo@liacs.nl \
--cc=vmiklos@frugalware.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).