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 19:02:26 +0800 [thread overview]
Message-ID: <46dff0320803030302t286c33a5h3555200c9e8840e3@mail.gmail.com> (raw)
In-Reply-To: <8c5c35580803022257n7ff0cdc3i1e72a0034d254aa4@mail.gmail.com>
On Mon, Mar 3, 2008 at 2:57 PM, Lars Hjemli <hjemli@gmail.com> wrote:
> On Mon, Mar 3, 2008 at 2:47 AM, Ping Yin <pkufranky@gmail.com> wrote:
> > But why always
> > use git init even when we don't have the local configuration
> > requirement?
>
> We need a way to tell git which of those submodules we are interested
> in, i.e. which submodules to clone/fetch during 'git submodule
> update'.
>
Now that's easy with the multiple level module definition. We can now
group our modules by hierachy and designate modules we are interested
by logical names such as crawler or search as my proposal has
mentioned.
And if there are not a logical module name satisfying our requirement,
we can define one by ourself in .git/config (if it's a special or
temporary requirement) or in .gitmodules (if it's a common
requirement).
Now .git/config and .gitmodules will play the same as
.git/info/exclude and .gitignore.
> --
> larsh
>
--
Ping Yin
next prev parent reply other threads:[~2008-03-03 11:03 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
2008-03-03 6:57 ` Lars Hjemli
2008-03-03 11:02 ` Ping Yin [this message]
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=46dff0320803030302t286c33a5h3555200c9e8840e3@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).