From: Kaartic Sivaraam <firstname.lastname@example.org>
To: Junio C Hamano <email@example.com>
Subject: Re: What's cooking in git.git (Dec 2017, #03; Wed, 13)
Date: Fri, 15 Dec 2017 20:59:32 +0530 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Thursday 14 December 2017 10:50 PM, Junio C Hamano wrote:
> Kaartic Sivaraam <email@example.com> writes:
>> It seems my series that fixes an error message in 'git-rebase'
>> (apart from a little cleanups) is missing. I guess I addressed the
>> issue that was raised in 3/3 as a v3 for that patch. Are any more
>> changes needed?
>> : <firstname.lastname@example.org>
>> : <email@example.com>
> I think you only sent 3/3 in newer rounds, which made it not to
> apply to my tree.
That's surprising, let me check.
> If you meant to drop changes in 1/3 and 2/3,
> perhaps because they were needless churn, then 3/3 needs to be
> updated not to depend on the changes these two made.
2/3 is for sure not needless. But 1/3 might be. Though I think it
improves the communicativity of the variable name. In case you think
it's completely useless, then I can drop it as we won't lose much anyway ??
next prev parent reply other threads:[~2017-12-15 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 23:00 Junio C Hamano
2017-12-14 12:37 ` Kaartic Sivaraam
2017-12-14 17:20 ` Junio C Hamano
2017-12-14 21:08 ` Junio C Hamano
2017-12-16 6:06 ` Kaartic Sivaraam
2017-12-14 21:09 ` [PATCH v4 2/3] rebase: distinguish user input by quoting it Junio C Hamano
2017-12-14 21:09 ` [PATCH v4 3/3] rebase: rebasing can also be done when HEAD is detached Junio C Hamano
2017-12-15 15:29 ` Kaartic Sivaraam [this message]
2017-12-14 17:41 ` What's cooking in git.git (Dec 2017, #03; Wed, 13) Ævar Arnfjörð Bjarmason
2017-12-14 21:04 ` Jonathan Nieder
2017-12-14 21:06 ` Junio C Hamano
2017-12-14 21:26 ` Jonathan Nieder
2017-12-15 12:39 ` Johannes Schindelin
2018-01-09 12:59 ` Lars Schneider
2018-01-09 18:59 ` Junio C Hamano
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:
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 \
* 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 inbox:
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).