Re: What's cooking in git.git (Oct 2013, #04; Fri, 18)

[Felipe Contreras <felipe.contreras@gmail.com>]

Jeff King wrote:
> 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?

I say they shouldn't be, unless the next version after 1.8 is 2.0. There should
be a separate branch for 2.0.

-- 
Felipe Contreras