From: Sven Verdoolaege <skimo@kotnet.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Dmitry Kakurin <dmitry.kakurin@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: Submodules
Date: Wed, 08 Aug 2007 21:53:51 +0200 [thread overview]
Message-ID: <20070808195351.GQ999MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <7vhcn94y9l.fsf@assigned-by-dhcp.cox.net>
On Wed, Aug 08, 2007 at 12:33:26PM -0700, Junio C Hamano wrote:
> + Note that the current submodule support is minimal and this is
> + deliberately so. A design decision we made is that operations
> + at the supermodule level do not recurse into submodules by
> + default. The expectation is that later we would add a
> + mechanism to tell git which submodules the user is interested
> + in, and this information might be used to determine the
> + recursive behaviour of certain commands (e.g. "git checkout"
> + and "git diff"), but currently we haven't agreed on what that
> + mechanism should look like. Therefore, if you use submodules,
> + you would probably need "git submodule update" on the
> + submodules you care about after running a "git checkout" at
> + the supermodule level.
> +
Maybe you could be a bit more explicit about the
possibly unexpected results of "git checkout".
Perhaps something like the following instead of the
last sentence:
In particular, if you have any submodules checked out,
running a "git checkout" at the supermodule level will
not update these submodules. They will therefore appear
to be modified (to the state prior to the checkout)
to any subsequent git command, until they have been
updated explicitly using "git submodule update".
skimo
next prev parent reply other threads:[~2007-08-08 19:53 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 ` Submodules Sven Verdoolaege
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 ` Sven Verdoolaege [this message]
-- 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=20070808195351.GQ999MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=dmitry.kakurin@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).