From: "Ping Yin" <pkufranky@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC v2] git-submodule: multi-level module definition
Date: Thu, 6 Mar 2008 13:18:17 +0800 [thread overview]
Message-ID: <46dff0320803052118j2296a2d4p397fa889f8cea45b@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0803060330210.15786@racer.site>
On Thu, Mar 6, 2008 at 10:32 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>
> > > The place the owner of the repository (not the project) expresses which
> > > modules are of interest, what transports she wants to use to access it,
> > > etc. is $GIT_DIR/config, and .gitmodules is a vehicle to supply hints to
> > > be used when the user populates that information.
> > >
> > Not always the case.
>
> If it is _not_ always the case, .gitmodules is definitely the wrong place,
> and $GIT_DIR/config is.
>
> Just like we need "init && update", and not have "init" update implicitly,
> like some people wish (who forget that other people might have other
> wishes), we need to allow for different options here.
>
> And as .gitmodules is _meant_ to be tracked, it is not the place to
> express individual wishes differing from the colleagues' wishes.
>
As an analogy, .gitignore is for colleagues' wishes and
.git/info/exluces is for individual wishes.
The same, .gitmodules is for colleagues' wishes and .git/config is for
individual wishes.
There are always common cases and special cases, so we need a machinsm
to support both of them.
> Ciao,
> Dscho
>
>
--
Ping Yin
next prev parent reply other threads:[~2008-03-06 5:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 16:04 [PATCH/RFC v2] git-submodule: multi-level module definition Ping Yin
2008-03-04 16:12 ` Johannes Schindelin
2008-03-05 2:13 ` Ping Yin
[not found] ` <7bfdc29a0803041917j16112e80uc0b21707bdfd3fe@mail.gmail.com>
[not found] ` <46dff0320803042315t2d89eb6fl325b4b2ef8ddbc44@mail.gmail.com>
2008-03-05 7:16 ` Ping Yin
2008-03-05 7:40 ` Imran M Yousuf
2008-03-05 7:53 ` Ping Yin
2008-03-05 8:03 ` Imran M Yousuf
2008-03-05 23:18 ` Junio C Hamano
2008-03-06 1:54 ` Ping Yin
2008-03-06 2:16 ` Imran M Yousuf
2008-03-06 2:32 ` Johannes Schindelin
2008-03-06 5:18 ` Ping Yin [this message]
2008-03-06 3:48 ` Junio C Hamano
2008-03-06 5:48 ` Ping Yin
2008-03-07 1:43 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46dff0320803052118j2296a2d4p397fa889f8cea45b@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).