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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
