Re: What's cooking in git.git (Mar 2017, #11; Mon, 27)
- From
Stefan Beller <sbeller@google.com>
- Date
- Mar 28, 2017, 16:56 UTC
- Message-ID
- <CAGZ79kY=jLJSCCT7MAsvurzRAS+LJKkwt=4HWGgu8nkg0ZXN4Q@mail.gmail.com>
- In-Reply-To
- <xmqqlgrqz6ta.fsf@gitster.mtv.corp.google.com>
Show 17 quoted lines
> * sb/submodule-short-status (2017-03-27) 7 commits > - submodule.c: correctly handle nested submodules in is_submodule_modified > - short status: improve reporting for submodule changes > - submodule.c: stricter checking for submodules in is_submodule_modified > - submodule.c: port is_submodule_modified to use porcelain 2 > - submodule.c: convert is_submodule_modified to use strbuf_getwholeline > - submodule.c: factor out early loop termination in is_submodule_modified > - submodule.c: use argv_array in is_submodule_modified > > The output from "git status --short" has been extended to show > various kinds of dirtyness in submodules differently; instead of to > "M" for modified, 'm' and '?' can be shown to signal changes only > to the working tree of the submodule but not the commit that is > checked out. > > Waiting for further comments. > The endgame looked mostly OK.
I will reroll the top most commit
> - submodule.c: correctly handle nested submodules in is_submodule_modified
per jrnieder's request to explain itself more (via tests, documentation)
Thanks, Stefan