From: Sven Verdoolaege <skimo@kotnet.org>
To: "martin f. krafft" <madduck@madduck.net>
Cc: git@vger.kernel.org, hjemli@gmail.com
Subject: Re: [PATCH] Clarify role of init command in git-submodules documentation
Date: Mon, 20 Aug 2007 09:54:59 +0200 [thread overview]
Message-ID: <20070820075459.GY1070MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <11875937841178-git-send-email-madduck@madduck.net>
On Mon, Aug 20, 2007 at 09:09:44AM +0200, martin f. krafft wrote:
> FILES
> -----
> -When initializing submodules, a .gitmodules file in the top-level directory
> -of the containing repository is used to find the url of each submodule.
> -This file should be formatted in the same way as $GIR_DIR/config. The key
> -to each submodule url is "submodule.$name.url".
> +To work with submodules, a user has to prepare a repository clone with the
I think this is a bit ambiguous.
> +command `git-submodule init`. This command copies the url of each submodule
As you can see in the "init" section of the man pages, the url is only
copied if it's not there already.
> +listed in the .gitmodules file in the top-level directory of the containing
> +repository to $GIT_DIR/config. The key to each submodule url is
> +"submodule.$name.url".
> +
> +The .gitmodules file then specifies the location of each submodule with
> +respect to the repository (and is shared among all contributors), while the
> +url of each submodule comes from the local configuration in $GIT_DIR/config
> +and can thus be modified independently of all other users.
This is better than the previous version, but in my mind still a bit confusing.
Let me have a go:
.gitmodules::
This file specifies the location of each submodule with respect
to the top-level directory of the git working tree as well as
the default url of each submodule. This default url is ignored
by all git submodule subcommands, except init. The latter can
be used to initialize the url in $GIR_DIR/config, which is the
url used by the other subcommands. This file is typically
tracked as it contains information that is shared by all
contributors. See also: gitlink:gitmodules[5].
$GIT_DIR/config::
This files contains the url of each submodule in "submodule.$name.url".
These urls are required by git submodule subcommands such as update
and can be initialized by calling "git submodule init".
The urls are specified in the local $GIT_DIR/config as the most
appropriate url to get updates from may by different for different users
and should not depend on the particular revision of the superproject
that is currently checked out.
skimo
next prev parent reply other threads:[~2007-08-20 7:55 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 [this message]
2007-08-21 18:02 ` martin f krafft
2007-08-21 20:25 ` Sven Verdoolaege
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=20070820075459.GY1070MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=git@vger.kernel.org \
--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).