From: Jeff King <peff@peff.net>
Date: Sat, 19 Oct 2013 06:34:48 GMT
Subject: Re: What's cooking in git.git (Oct 2013, #04; Fri, 18)
Message-ID: <20131019063447.GA18977@sigill.intra.peff.net>
In-Reply-To: <xmqq38nyw7ja.fsf@gitster.dls.corp.google.com>

On Fri, Oct 18, 2013 at 03:14:49PM -0700, Junio C Hamano wrote:

> * jn/add-2.0-u-A-sans-pathspec (2013-04-26) 1 commit
>  - git add: -u/-A now affects the entire working tree
> 
>  Will cook in 'next' until Git 2.0.
> 
> 
> * jc/core-checkstat-2.0 (2013-05-06) 1 commit
>  - core.statinfo: remove as promised in Git 2.0
> 
>  Will cook in 'next' until Git 2.0.
> 
> 
> * jc/push-2.0-default-to-simple (2013-06-18) 1 commit
>  - push: switch default from "matching" to "simple"
> 
>  Will cook in 'next' until Git 2.0.
> 
> 
> * jc/add-2.0-ignore-removal (2013-04-22) 1 commit
>  - git add <pathspec>... defaults to "-A"
> 
>  Updated endgame for "git add <pathspec>" that defaults to "--all"
>  aka "--no-ignore-removal".
> 
>  Will cook in 'next' until Git 2.0.

I notice that these are not actually in 'next', despite the
descriptions.  Should they be, to give them wider exposure?

-Peff