git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Verdoolaege <skimo@kotnet.org>
To: martin f krafft <madduck@madduck.net>
Cc: git@vger.kernel.org, hjemli@gmail.com,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Clarify role of init command in git-submodules documentation
Date: Wed, 22 Aug 2007 10:30:32 +0200	[thread overview]
Message-ID: <20070822083032.GN1070MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <20070821210349.GA16702@piper.oerlikon.madduck.net>

On Tue, Aug 21, 2007 at 11:03:49PM +0200, martin f krafft wrote:
> also sprach Sven Verdoolaege <skimo@kotnet.org> [2007.08.21.2225 +0200]:
> > >   Users who clone the project's repository need to initialize each
> > >   submodule before they can work with it. By initializing
> > 
> > I suppose this is implicit in the git submodule man page,
> 
> It wasn't to me; that's why I am doing all this.

I meant that the rest of my sentence could probably be
implicitly understood.

> > but this is only true if you actually want to use git submodule to
> > work with the submodules.
> 
> Is it? I tried this and after cloning a repo with submodules, it
> created the submodule directories alright, but it did not actually
> check them out/populate them, so they were empty.

Some people have been doing this manually or have homegrown scripts.
Not that you should mention those options here.

> 
> > >   a submodule, the submodule's url is copied from the
> > >   .gitmodules
> > 
> > As I mentioned before, this is not strictly true. (see init::)
> 
> You're missing something like "... unless the submodule is already
> registered, in which case it won't be overwritten", right?

Something like that, yes.

skimo

  reply	other threads:[~2007-08-22  8:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 16:20 git submodule init and redundant data in .gitmodules/.git/config martin f krafft
2007-08-15 16:38 ` Sven Verdoolaege
2007-08-15 22:29   ` using .gitmodule as default (was: git submodule init and redundant data in .gitmodules/.git/config) martin f krafft
2007-08-16 13:53     ` Josef Weidendorfer
2007-08-16 14:21       ` martin f krafft
2007-08-16 16:39         ` Josef Weidendorfer
2007-08-16 18:10       ` [PATCH] clarify need for init in git-submodules documentation martin f. krafft
2007-08-17  9:31         ` Sven Verdoolaege
2007-08-17 10:08           ` martin f krafft
2007-08-17 10:36             ` Sven Verdoolaege
2007-08-20  7:09               ` [PATCH] Clarify role of init command " martin f. krafft
2007-08-20  7:54                 ` Sven Verdoolaege
2007-08-21 18:02                   ` martin f krafft
2007-08-21 20:25                     ` Sven Verdoolaege
2007-08-21 21:03                       ` martin f krafft
2007-08-22  8:30                         ` Sven Verdoolaege [this message]
2007-08-22 13:48                           ` martin f krafft
2007-08-20 21:14                 ` Junio C Hamano
2007-08-20  9:29           ` Not setting M-F-T, keeping people on Cc (was: [PATCH] clarify need for init in git-submodules documentation) martin f krafft
2007-08-17  7:14     ` using .gitmodule as default (was: git submodule init and redundant data in .gitmodules/.git/config) Lars Hjemli

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=20070822083032.GN1070MdfPADPa@greensroom.kotnet.org \
    --to=skimo@kotnet.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hjemli@gmail.com \
    --cc=madduck@madduck.net \
    --cc=skimo@liacs.nl \
    /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).