From: Junio C Hamano <gitster@pobox•com>
To: Pranit Bauva <pranit.bauva@gmail•com>
Cc: Git List <git@vger•kernel.org>, Eric Sunshine <sunshine@sunshineco•com>
Subject: Re: What's cooking in git.git (Apr 2016, #06; Thu, 21)
Date: Fri, 22 Apr 2016 15:12:30 -0700 [thread overview]
Message-ID: <xmqq7ffpnvht.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqq60v9r20i.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Fri, 22 Apr 2016 10:23:25 -0700")
Junio C Hamano <gitster@pobox•com> writes:
>>> Is this going to be rerolled?
>>> ($gmane/291382)
>>
>> The changes weren't that big enough and I had my end semester exams
>> coming so I decided not to re-roll it.
>> If you think contrary, I can do a re-roll with the changes suggested
>> by Eric Sunshine.
>
> I agree that this was pretty close to be done. Let me see if I can
> find time to finish it up in the coming few days.
I looked at the reviews again and I take the above back--the end
result of applying all patches may not have to change a lot, but
the ordering and structure of the series may need cleanign up.
next prev parent reply other threads:[~2016-04-22 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 22:20 What's cooking in git.git (Apr 2016, #06; Thu, 21) Junio C Hamano
2016-04-21 22:32 ` Stefan Beller
2016-04-21 22:48 ` Pranit Bauva
2016-04-22 17:23 ` Junio C Hamano
2016-04-22 22:12 ` Junio C Hamano [this message]
2016-04-23 18:42 ` Pranit Bauva
2016-04-21 22:51 ` Santiago Torres
2016-04-21 23:20 ` Junio C Hamano
2016-04-22 4:42 ` Jeff King
2016-04-22 17:22 ` Junio C Hamano
2016-04-22 18:38 ` Jeff King
2016-04-22 5:01 ` Torsten Bögershausen
2016-04-22 17:23 ` Junio C Hamano
2016-04-22 14:04 ` Johannes Schindelin
2016-04-22 17:24 ` 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=xmqq7ffpnvht.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=pranit.bauva@gmail$(echo .)com \
--cc=sunshine@sunshineco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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