Re: [PATCH] status&commit: Teach them to show commits of modified submodules.

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] status&commit: Teach them to show commits of modified submodules.

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:46

How does this work when you are a toplevel developer and do not
have the submodule cloned and checked out?

Our code should treat having the submodule directory and not
having it when there is a mode 160000 entry in the index equally
likely.  Cloning and checking-out is _not_ the norm (nor the
exception).

Re: [PATCH] status&commit: Teach them to show commits of modified submodules.

From: Yin Ping <hidden>
Date: 2016-06-15 22:43:46

On 11/3/07, Junio C Hamano [off-list ref] wrote:
How does this work when you are a toplevel developer and do not
have the submodule cloned and checked out?

Our code should treat having the submodule directory and not
having it when there is a mode 160000 entry in the index equally
likely.  Cloning and checking-out is _not_ the norm (nor the
exception).
When submodule is not cheched out, it is never modified. In this case
modules variable will be empty ( since git diff --cached is used) and
the corrosponding module directory will not be checked. So the output
will be the same as the original output.



-- 
franky
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help