All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Samuel Lijin <sxlijin@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>,
	David Turner <dturner@twosigma.com>,
	Ben Peart <benpeart@microsoft.com>
Subject: Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)
Date: Fri, 2 Jun 2017 12:11:53 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1.1706021211300.171564@virtualbox> (raw)
In-Reply-To: <xmqqfufj47oz.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Fri, 2 Jun 2017, Junio C Hamano wrote:

> Samuel Lijin <sxlijin@gmail.com> writes:
> 
> >> What is holding this topic up? Anything Ben or I can do to move this
> >> closer to `next` or even `master`?
> >
> > It's in `next` right now (3196d093d6).
> 
> Thanks for pinging and checking ;-)  
> 
> I think the topic was merged to 'next' on the 23rd of last month and
> graduated to 'master' in the past few days, together with other
> topics.

Okay. I never saw any "Will merge to" message, so I got worried.

Thanks,
Dscho

  reply	other threads:[~2017-06-02 10:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01  7:44 What's cooking in git.git (Jun 2017, #01; Thu, 1) Junio C Hamano
2017-06-01 18:56 ` preserve untracked cache, was " Johannes Schindelin
2017-06-01 19:16   ` Samuel Lijin
2017-06-01 23:19     ` Junio C Hamano
2017-06-02 10:11       ` Johannes Schindelin [this message]
2017-06-03  0:26         ` Junio C Hamano
2017-06-15 10:34           ` Johannes Schindelin
2017-06-01 21:06 ` Johannes Sixt
2017-06-01 23:14   ` 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=alpine.DEB.2.21.1.1706021211300.171564@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=benpeart@microsoft.com \
    --cc=dturner@twosigma.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sxlijin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.