Re: What's cooking in git.git (Oct 2009, #02; Sun, 11)

From: Jeff King <peff@peff.net>
Date: Oct 12, 2009, 05:14 UTC
Message-ID: <20091012051442.GB23007@coredump.intra.peff.net>
In-Reply-To: <7vfx9pmhae.fsf@alter.siamese.dyndns.org>

On Sun, Oct 11, 2009 at 08:18:17PM -0700, Junio C Hamano wrote:

Show 21 quoted lines

> * 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 can always revert selectively, but I though the post-v1.6.5 rewind would be a good time to re-order.

-Peff