git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] git-submodule: multiple-level modules definition

From
Ping Yin <pkufranky@gmail.com>
Date
Mar 3, 2008, 01:47 UTC
Message-ID
<46dff0320803021747y6e334903pf8b5a77168bc7882@mail.gmail.com>
In-Reply-To
<8c5c35580803021018v7590ad76kbbab2b1113e27666@mail.gmail.com>
On Mon, Mar 3, 2008 at 2:18 AM, Lars Hjemli <hjemli@gmail.com> wrote:
Show 12 quoted lines
> 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
Previous: Lars HjemliNext: Lars Hjemli
Message 3 of 8 in “[RFC] git-submodule: multiple-level modules definition”
  1. Ping YinMar 2, 2008
  2. Lars HjemliMar 2, 2008
  3. Ping YinMar 3, 2008
  4. Lars HjemliMar 3, 2008
  5. Ping YinMar 3, 2008
  6. Lars HjemliMar 3, 2008
  7. Ping YinMar 3, 2008
  8. Ping YinMar 4, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.