Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>, Paul Tan <pyokagan@gmail.com>
Subject: Re: What's cooking in git.git (Aug 2015, #01; Mon, 3)
Date: Mon, 03 Aug 2015 18:12:52 -0700	[thread overview]
Message-ID: <xmqqsi7z6eln.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAPig+cQr6tZeYwH3W4NP9_6udD2qz7t6vFR7n4haqJLrNhM62w@mail.gmail.com> (Eric Sunshine's message of "Mon, 3 Aug 2015 18:41:02 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Mon, Aug 3, 2015 at 6:18 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> I've kicked a few topics out of 'next' back to 'pu' for now.
>>  - I think es/worktree-add and es/worktree-add-cleanup are good
>>    shape overall, but we probably would want to make them into a
>>    single topic.
>
> Is there anything I need to do to move this along, or is it something
> you will be handling locally?

Unless you view this as a chance to rebuild the topic and want to
take advantage of it, e.g. "I'd like to reorder and replace 4-7 with
these two patches while it is outside 'next'", there is no need to
do anything on your part (this comment also applies to Paul).  I
just wanted to eyeball the result after I twiddled a few topics with
"maybe squash this in?" patches we saw recently before merging them
back into 'next'.

Thanks.

  reply	other threads:[~2015-08-04  1:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 22:18 What's cooking in git.git (Aug 2015, #01; Mon, 3) Junio C Hamano
2015-08-03 22:41 ` Eric Sunshine
2015-08-04  1:12   ` Junio C Hamano [this message]
2015-08-04  0:16 ` Paul Tan
2015-08-04  1:13   ` 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=xmqqsi7z6eln.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pyokagan@gmail.com \
    --cc=sunshine@sunshineco.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