From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)
Date: Sat, 16 Sep 2017 05:33:00 +0900 [thread overview]
Message-ID: <xmqqk20zwvlv.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1709152113070.219280@virtualbox> (Johannes Schindelin's message of "Fri, 15 Sep 2017 21:14:09 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Please stop stating that you expect a reroll for rebase-i-extra when you
> explicitly stated months ago that you would not take my v6. It gets a bit
> annoying.
I already explained to you why I skipped v6, which turned to be
identical to v5 when the unnecessary rebase was undone. It does not
have anything to do with expecting a v7 or later to fix other things
already pointed out in the review.
Having said that, I am getting sick of your constant hostile
whining, and am inclined to merge it as-is to 'next' and advance it
from there, if only to reduce these noises from you. Even if you
are unwilling to, you do not have the sole possession and veto power
over the area of the code (neither do I) to prevent further
improvements, so I can expect others with good design taste
(hopefully not me) to fix up the misuse of revision traversal
implementation detail with follow-up patches.
next prev parent reply other threads:[~2017-09-15 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 5:58 What's cooking in git.git (Sep 2017, #03; Fri, 15) Junio C Hamano
2017-09-15 7:50 ` Lars Schneider
2017-09-19 1:18 ` Junio C Hamano
2017-09-15 19:14 ` Johannes Schindelin
2017-09-15 20:33 ` Junio C Hamano [this message]
2017-09-15 19:23 ` Johannes Schindelin
2017-09-15 20:49 ` Junio C Hamano
2017-09-29 11:39 ` Johannes Schindelin
2017-09-21 21:14 ` Sahil Dua
2017-09-22 0:59 ` Junio C Hamano
2017-09-22 3:39 ` Junio C Hamano
2017-09-24 16:16 ` Sahil Dua
2017-09-25 0:40 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqk20zwvlv.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).