git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ping Yin" <pkufranky@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH/RFC v2] git-submodule: multi-level module definition
Date: Wed, 5 Mar 2008 10:13:17 +0800	[thread overview]
Message-ID: <46dff0320803041813y2d2acfddjb7f973a54e5d64c9@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0803041608420.22527@racer.site>

On Wed, Mar 5, 2008 at 12:12 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>  In "git remote", we also have a notion of groups.  It looks much nicer,
>  IMO.  So why not do this?
>
>  [submodules]
>         service = crawler search
>         crawler = util imcrawler
>         search = util imsearch
>
Hmm, it seems more brief.
>
>  However, I think that being able to specify submodule groups recursively
>  is only adding to confusion, so I would even prefer this:
>
>  [submodules]
>         service = util imcrawler imsearch
>         crawler = util imcrawler
>         search = util imsearch
>  [...]
>
This is fine when number of modules is not much, or user may feel
inconvenient since they have to type so many module names.
A hierarchy of modules can help much when having a group of common
modules which should be included in most of role-related logical
moduels.
>  Ciao,
>  Dscho
>



-- 
Ping Yin

  reply	other threads:[~2008-03-05  2:13 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 [this message]
     [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
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=46dff0320803041813y2d2acfddjb7f973a54e5d64c9@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).