Jeff King <peff@xxxxxxxx> writes: > On Tue, Sep 01, 2009 at 09:26:26PM -0700, Junio C Hamano wrote: > >> But not everybody is used to such a set-up. If you rely on terminal's >> scrollback buffer with mouse and a short terminal, I can see cutting and >> pasting would be an issue. I do not have a good answer to "tig status", >> but the design principle of supporting the lowest denominator is >> important. > > But I'm not sure it is about "lowest common denominator". I think it is > about different people having different preferences (as a matter of > fact, I use an 80x25 terminal most of the time, and I think I prefer the > content at the top. Perhaps it is simply habit, but I do think having it > right next to "staged for commit" items makes the most sense). > ... Here is how I would justify the change (the patch is the same as Hannes's first version. From: Johannes Sixt <j6t@xxxxxxxx> Date: Tue, 1 Sep 2009 22:13:53 +0200 Subject: [PATCH] status: list unmerged files much later When resolving a conflicted merge, two lists in the status output need more attention from the user than other parts. - the list of updated paths is useful to review the amount of changes the merge brings in (the user cannot do much about them other than reviewing, though); and - the list of unmerged paths needs the most attention from the user; the user needs to resolve them in order to proceed. Since the output of git status does not by default go through the pager, the early parts of the output can scroll away at the top. It is better to put the more important information near the bottom. During a merge, local changes that are not in the index are minimum, and you should keep the untracked list small in any case, so moving the unmerged list from the top of the output to immediately after the list of updated paths would give us the optimum layout.. Signed-off-by: Johannes Sixt <j6t@xxxxxxxx> Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> --- wt-status.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) -- 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