Re: [PATCH] Clarify role of init command in git-submodules documentation
- From
- martin f krafft <madduck@madduck.net>
- Date
- Aug 22, 2007, 13:48 UTC
- Message-ID
- <20070822134825.GA14589@piper.oerlikon.madduck.net>
- In-Reply-To
- <20070822083032.GN1070MdfPADPa@greensroom.kotnet.org>
also sprach Sven Verdoolaege <skimo@kotnet.org> [2007.08.22.1030 +0200]:
Show 6 quoted lines
> > > I suppose this is implicit in the git submodule man page, > > > but this is only true if you actually want to use git submodule to > > > work with the submodules. > > > I meant that the rest of my sentence could probably be > implicitly understood.
Ah. Okay, well, I'd say since this is the git-submodule manpage, we can assume that they want to work with git-submodule.
Show 6 quoted lines
> > 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.
Ok.
> > You're missing something like "... unless the submodule is already > > registered, in which case it won't be overwritten", right? > > Something like that, yes.
Consider it done. Patch forthcoming, though probably not tonight, I also want to give others more time to comment.
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
"of course the music is a great difficulty.
you see, if one plays good music, people don't listen,
and if one plays bad music people don't talk."
-- oscar wilde
spamtraps: madduck.bogus@madduck.net