On Mon, May 07, 2012 at 05:25:04PM -0400, Jeff King wrote: > There is no reason not to, as the user has to explicitly ask > for it, so we are not breaking compatibility by doing so. We > can do this simply by moving the "show_branch" flag into > the wt_status struct. As a bonus, this saves us from passing > it explicitly, simplifying the code. I forgot this, which should probably be squashed in: -- >8 -- Subject: status: fix "--porcelain -z -b" documentation It is no longer the case that "-z" will not respect "-b". Signed-off-by: Jeff King <peff@xxxxxxxx> --- Documentation/git-status.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt index 2883a28..67e5f53 100644 --- a/Documentation/git-status.txt +++ b/Documentation/git-status.txt @@ -184,7 +184,7 @@ order is reversed (e.g 'from \-> to' becomes 'to from'). Second, a NUL and the terminating newline (but a space still separates the status field from the first filename). Third, filenames containing special characters are not specially formatted; no quoting or -backslash-escaping is performed. Fourth, there is no branch line. +backslash-escaping is performed. CONFIGURATION ------------- -- 1.7.10.1.12.gd79f7ab -- 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