git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2013, #04; Fri, 18)
Date: Sat, 19 Oct 2013 02:34:48 -0400	[thread overview]
Message-ID: <20131019063447.GA18977@sigill.intra.peff.net> (raw)
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

  reply	other threads:[~2013-10-19  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 22:14 What's cooking in git.git (Oct 2013, #04; Fri, 18) Junio C Hamano
2013-10-19  6:34 ` Jeff King [this message]
2013-10-19  7:35   ` Felipe Contreras
2013-10-22 15:20   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131019063447.GA18977@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).