Historically, git status needed to prefix each output line with '#' so
that the output could be added as comment to the commit message. This
prefix comment has no real purpose when git status is ran from the
command-line, and this may distract users from the real content.
Allow the user to
Am 8/28/2013 10:32, schrieb Matthieu Moy:
Historically, git status needed to prefix each output line with '#' so
that the output could be added as comment to the commit message. This
prefix comment has no real purpose when git status is ran from the
command-line, and this may distract users
Johannes Sixt j.s...@viscovery.net writes:
How does your solution work when dirty submodules are involved and
submodule status is included?f
Badly ;-).
I didn't notice the subcommand call for submodules summary. It's a bit
more tricky to get right, as the git sumbodule summary --for-status
3 matches
Mail list logo