Jeff King <peff@xxxxxxxx> writes: > On Sun, Oct 11, 2009 at 08:18:17PM -0700, Junio C Hamano wrote: > >> * jk/1.7.0-status (2009-09-05) 5 commits. >> - docs: note that status configuration affects only long format >> (merged to 'next' on 2009-10-11 at 65c8513) >> + commit: support alternate status formats >> + status: add --porcelain output format >> + status: refactor format option parsing >> + status: refactor short-mode printing to its own function >> (this branch uses jc/1.7.0-status.) >> >> Gives the --short output format to post 1.7.0 "git commit --dry-run" that >> is similar to that of post 1.7.0 "git status". >> >> * jc/1.7.0-status (2009-09-05) 4 commits. >> (merged to 'next' on 2009-10-11 at 9558627) >> + status: typo fix in usage >> + git status: not "commit --dry-run" anymore >> + git stat -s: short status output >> + git stat: the beginning of "status that is not a dry-run of commit" >> (this branch is used by jk/1.7.0-status.) >> >> With this, "git status" is no longer "git commit --dry-run". > > Hmm. I thought you wanted to re-order some of these for to put the > porcelain and short formats into v1.6.6, but leave the status switchover > for v1.7.0. We could build an alternate history between 3fa509d..46b77a6, revert the merges 9558627 and 65c8513, and merge the alternate history. But is the short format support so solid that it deserves to be in 1.6.6 in the current shape? -- 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