Thread (6 messages) flat view 6 messages, 3 authors, 2016-06-15

Re: Possible bug with git status in 1.7.0

From: Jens Lehmann <hidden>
Date: 2016-06-15 22:48:18

Am 19.02.2010 17:42, schrieb Sergio Callegari:
Yes! My ideal behavior (if I am not asking too much) would be trying to
keep the status as little wordy as possible (1 line per submodule)

e.g. something like

#       modified module (commit id):   mod1
#       modified module (modified files): mod2
#    modified module (untracked files): mod3
#       modified module (modified files, untracked files): mod4
#    modified module (commit id, modified files, untracked files): mod5
Yup, one line per submodule should be enough. But maybe it's nicer to
have the details /after/ the submodule name:

#	modified:   mod1 (Submodule has new commit(s), modified content, untracked content)

Then it fits more nicely with the output for files, no?

We could drop the "Submodule has " if people see it as a waste of screen
estate. Also i have no strong feelings about "content", i just happen to
think it is more appropriate as submodules can contain not only files but
other submodules too. Opinions?

Will send a patch for discussion as soon as i have something to show ...
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help