It is a bit too much to keep sending the full report every night, so I'll send out some highlights since issue #09 of this month for tonight. Short term plans ---------------- Will merge to "master". + jb/required-filter 02-17/02-26 #1 + ph/cherry-pick-advice-refinement 02-22/02-26 #1 + pj/completion-remote-set-url-branches 02-22/02-26 #2 Will merge to "next" - cn/maint-branch-with-bad 02-27 #1 - jk/symbolic-ref-short 02-27 #1 Will merge to "next", perhaps? - jn/gitweb-hilite-regions 02-26 #4 - th/git-diffall 02-27 #1 Notable topics that may need more discussion -------------------------------------------- I will not list the stalled topics here and harrass owners of them here. * zj/diff-stat-dyncol (2012-02-27) 11 commits - diff --stat: add config option to limit graph width - diff --stat: enable limiting of the graph part - diff --stat: add a test for output with COLUMNS=40 - diff --stat: use a maximum of 5/8 for the filename part - merge --stat: use the full terminal width - log --stat: use the full terminal width - show --stat: use the full terminal width - diff --stat: use the full terminal width - diff --stat: tests for long filenames and big change counts - t4014: addtional format-patch test vectors - Merge branches zj/decimal-width, zj/term-columns and jc/diff-stat-scaler I resurrected the additional tests for format-patch from an earlier round, as it illustrates the behaviour change brought by "5/8 split" very well. * nd/columns (2012-02-26) 11 commits - tag: add --column - column: support piping stdout to external git-column process - status: add --column - branch: add --column - help: reuse print_columns() for help -a - column: add column.ui for default column output settings - column: support columns with different widths - column: add columnar layout - Stop starting pager recursively - Add git-column and column mode parsing - column: add API to print items in columns Comments by Ramsay on the parsing code seemed reasonable. * cb/fsck-squelch-dangling (2012-02-26) 1 commit - fsck: do not print dangling objects by default Introduces "fsck --dangling" and removes the output for dangling objects from the default output. The first patch to advance this topic should add --[no-]dangling option and update the documentation to illustrate its use. On top of that, if we were to change the default not to show the dangling objects, deprecation patches that span longer timeperiod need to be built, but the follow-on patches and the default change may not be necessary, given that the command is "fsck". * rs/no-no-no-parseopt (2012-02-26) 3 commits - parse-options: remove PARSE_OPT_NEGHELP - parse-options: allow positivation of options starting, with no- - test-parse-options: convert to OPT_BOOL() Options that use PARSE_OPT_NEGHELP needed to word their help text in a strange way, and this gets rid of the uses of them. I tend to agree with Peff that REVERSE_BOOL or NEGBIT based solution may be more readable in the longer term. As the options that used the funny NEGHELP are limited, the difference between two approaches may not matter too much, but then that argues against fixing the funny help messages, so... -- 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