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 (preview)
Date: Mon, 09 Jan 2017 07:05:15 -0800 [thread overview]
Message-ID: <xmqqmvf0uvdg.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1701091228460.3469@virtualbox> (Johannes Schindelin's message of "Mon, 9 Jan 2017 12:36:52 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Junio,
>
> On Sun, 8 Jan 2017, Junio C Hamano wrote:
>
>> * js/difftool-builtin (2017-01-08) 4 commits
>> - t7800: run both builtin and scripted difftool, for now
>> - difftool: implement the functionality in the builtin
>> - difftool: add a skeleton for the upcoming builtin
>> - git_exec_path: avoid Coverity warning about unfree()d result
>>
>> Rewrite a scripted porcelain "git difftool" in C.
>>
>> What's the doneness of this topic?
>
> There was only one bug report since the first iteration, and it has been
> fixed as of v4.
This is more RFH than FYI, but some topics in flight add more tests
to t7800 and with everything merged, the test breaks at the tip of
'pu' as of tonight (eh, technically last night, as I ended up not
sleeping due to jetlag), even though each individual topic passes
it. It _might_ indicate a problem with this topic, or it may merely
be a biproduct of a mismerge.
prev parent reply other threads:[~2017-01-09 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 3:36 What's cooking in git.git (preview) Junio C Hamano
2017-01-09 11:36 ` Johannes Schindelin
2017-01-09 15:05 ` Junio C Hamano [this message]
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=xmqqmvf0uvdg.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).