git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Verdoolaege <skimo@kotnet.org>
To: Dmitry Kakurin <dmitry.kakurin@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Submodules
Date: Wed, 08 Aug 2007 12:41:17 +0200	[thread overview]
Message-ID: <20070808104117.GK999MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <a1bbc6950708071631w5d232e92gd0fa27158b27b5c3@mail.gmail.com>

On Tue, Aug 07, 2007 at 04:31:57PM -0700, Dmitry Kakurin wrote:
> This is exactly the level of details I'm talking about:
> * how come sumbodules are not initialized when I do a clone of super.

See you second question.

> I expect to be able to build super after I clone it. Is there a new
> (undocumented) flag to clone?

Not (yet).  Right now, you have to do

git submodule init
git submodule update

after you clone to fetch and check-out all (first-level) submodules.

> * is it OK to *not* init a submodule? will super become unhappy? Can I
> do commits to super in this case?

Yes. No. Yes.
In fact, only the "git submodule" subcommand are affected by a
"git submodule init".  Doing a "git submodule update" will actually
check out the submodules and from then on, the HEAD of this checked-out
submodule will be considered the content of the submodule in
the working tree of the supermodule.

> * why submodules should be listed in 2 places: in .submodules and in
> super/.git/config?

It only has to be specified in .git/config.
The value in .gitmodules (if present) is used by "git submodule init"
as a default value for the one in .git/config.

skimo

  parent reply	other threads:[~2007-08-08 10:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 22:37 Submodules Dmitry Kakurin
2007-08-07 22:49 ` Submodules Johannes Schindelin
2007-08-07 23:10   ` Submodules Dmitry Kakurin
2007-08-08 10:27     ` Submodules Sven Verdoolaege
2007-08-07 22:50 ` Submodules Johannes Schindelin
2007-08-07 23:31   ` Submodules Dmitry Kakurin
2007-08-08  0:07     ` Submodules Johannes Schindelin
2007-08-08 10:41     ` Sven Verdoolaege [this message]
2007-08-08 19:33       ` Submodules Junio C Hamano
2007-08-08 19:40         ` Submodules Johannes Schindelin
2007-08-08 19:59           ` Submodules Junio C Hamano
2007-08-08 20:08             ` Submodules Sven Verdoolaege
2007-08-08 22:08               ` Submodules Junio C Hamano
2007-08-08 22:18                 ` Submodules Johannes Schindelin
2007-08-08 20:27             ` Submodules Junio C Hamano
2007-08-08 20:47           ` Submodules Andy Parkins
2007-08-08 21:12             ` Submodules Johannes Schindelin
2007-08-09  5:44               ` Submodules Sven Verdoolaege
2007-08-08 19:53         ` Submodules Sven Verdoolaege
  -- strict thread matches above, loose matches on Subject: below --
2013-05-03 13:45 submodules shawn wilson
2013-05-03 19:51 ` submodules Jens Lehmann
2014-01-23  8:38 submodules shawn wilson
2014-01-23 17:20 ` submodules W. Trevor King

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=20070808104117.GK999MdfPADPa@greensroom.kotnet.org \
    --to=skimo@kotnet.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dmitry.kakurin@gmail.com \
    --cc=git@vger.kernel.org \
    --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).