From: "Ping Yin" <pkufranky@gmail.com>
To: "Lars Hjemli" <hjemli@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [RFC] git-submodule: multiple-level modules definition
Date: Mon, 3 Mar 2008 09:47:06 +0800 [thread overview]
Message-ID: <46dff0320803021747y6e334903pf8b5a77168bc7882@mail.gmail.com> (raw)
In-Reply-To: <8c5c35580803021018v7590ad76kbbab2b1113e27666@mail.gmail.com>
On Mon, Mar 3, 2008 at 2:18 AM, Lars Hjemli <hjemli@gmail.com> wrote:
> On Sun, Mar 2, 2008 at 6:11 PM, Ping Yin <pkufranky@gmail.com> wrote:
> > 4. Do we really need 'init' subcommand?
>
> Yes: .git/config tells git which submodule(s) the user is interested
> in and where to fetch updates from for these submodules, while
> .gitmodules is used to map a submodule _name_ to a submodule _path_
> and also to provide a url where submodule updates _can_ be fetched.
>
> So the actual use of submodules is strictly a local configuration
> issue and as such it needs to be kept in .git/config. And to help the
> user populate .git/config with submodule information we have 'git
> submodule init'.
Is it always a local configuration issue? In a project with hundreds
of submodule, will anybody modify the submodule url?
I think .gitmodules can be the default repository configuration, and
when we have local configuration issue, we can override the
configuration in .git/config with the help of git init. But why always
use git init even when we don't have the local configuration
requirement?
>
> --
> larsh
>
--
Ping Yin
next prev parent reply other threads:[~2008-03-03 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 17:11 [RFC] git-submodule: multiple-level modules definition Ping Yin
2008-03-02 18:18 ` Lars Hjemli
2008-03-03 1:47 ` Ping Yin [this message]
2008-03-03 6:57 ` Lars Hjemli
2008-03-03 11:02 ` Ping Yin
2008-03-03 11:51 ` Lars Hjemli
2008-03-03 12:45 ` Ping Yin
2008-03-04 13:27 ` Ping Yin
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=46dff0320803021747y6e334903pf8b5a77168bc7882@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
/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).