From: Sven Verdoolaege <skimo@kotnet.org>
To: martin f krafft <madduck@madduck.net>
Cc: git@vger.kernel.org, hjemli@gmail.com,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Clarify role of init command in git-submodules documentation
Date: Tue, 21 Aug 2007 22:25:16 +0200 [thread overview]
Message-ID: <20070821202516.GL1070MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <20070821180218.GA14739@piper.oerlikon.madduck.net>
On Tue, Aug 21, 2007 at 08:02:18PM +0200, martin f krafft wrote:
> FILES
I'm not sure this is the most appropriate name for this section.
> A repository with submodules is identified by a .gitmodules file
> in the repository's top level (see gitlink:gitmodules[5]). This
> file specifies for each submodule its name, the url of the
> submodule's repository, as well as the location of the submodule
> within the (super)project's repository. As the .gitmodules file
> contains information shared by all users of the repository, it is
> typically tracked.
>
> Users who clone the project's repository need to initialize each
> submodule before they can work with it. By initializing
I suppose this is implicit in the git submodule man page,
but this is only true if you actually want to use git submodule
to work with the submodules.
> a submodule, the submodule's url is copied from the .gitmodules
As I mentioned before, this is not strictly true.
(see init::)
> By pulling the submodule urls out of $GIT_DIR/config,
> git-submodule allows contributors to use different urls (e.g. via
I'm not a native speaker, but to me that sounds like you are _not_
using the urls in $GIT_DIR/config. That is, I read that as:
they are pulled out of $GIT_DIR/config (and then placed somewhere else).
Other than that, it's definitely an improvement.
skimo
next prev parent reply other threads:[~2007-08-21 20:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 16:20 git submodule init and redundant data in .gitmodules/.git/config martin f krafft
2007-08-15 16:38 ` Sven Verdoolaege
2007-08-15 22:29 ` using .gitmodule as default (was: git submodule init and redundant data in .gitmodules/.git/config) martin f krafft
2007-08-16 13:53 ` Josef Weidendorfer
2007-08-16 14:21 ` martin f krafft
2007-08-16 16:39 ` Josef Weidendorfer
2007-08-16 18:10 ` [PATCH] clarify need for init in git-submodules documentation martin f. krafft
2007-08-17 9:31 ` Sven Verdoolaege
2007-08-17 10:08 ` martin f krafft
2007-08-17 10:36 ` Sven Verdoolaege
2007-08-20 7:09 ` [PATCH] Clarify role of init command " martin f. krafft
2007-08-20 7:54 ` Sven Verdoolaege
2007-08-21 18:02 ` martin f krafft
2007-08-21 20:25 ` Sven Verdoolaege [this message]
2007-08-21 21:03 ` martin f krafft
2007-08-22 8:30 ` Sven Verdoolaege
2007-08-22 13:48 ` martin f krafft
2007-08-20 21:14 ` Junio C Hamano
2007-08-20 9:29 ` Not setting M-F-T, keeping people on Cc (was: [PATCH] clarify need for init in git-submodules documentation) martin f krafft
2007-08-17 7:14 ` using .gitmodule as default (was: git submodule init and redundant data in .gitmodules/.git/config) Lars Hjemli
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=20070821202516.GL1070MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hjemli@gmail.com \
--cc=madduck@madduck.net \
--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).