Re: What's cooking in git.git (Jan 2017, #02; Sun, 15)

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 16, 2017, 11:40 UTC
Message-ID: <alpine.DEB.2.20.1701161231530.3469@virtualbox>
In-Reply-To: <xmqqh94zbwlu.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Sun, 15 Jan 2017, Junio C Hamano wrote:

> Here are the topics that have been cooking.  Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.  The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.

A suggestion: since it is very, very tedious to find the latest iteration's thread, as well as the corresponding commit in `pu` (or whatever other branch you use), and since you auto-generate these lists anyway, it would make things less cumbersome if the commit names of the tips, as well as the Message-IDs of the cover-letter (or first patch) were displayed with the topic branches.

It still would not address e.g. the problem that the original authors are not notified about the current state of their submission by these What's Cooking mails.

But it would improve the situation.

Show 5 quoted lines

> * js/difftool-builtin (2017-01-09) 5 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: do not return the result of getenv()

This patch was not in my patch submission. Sneaking it into this topic branch is not incorrect.

It does not matter, though, as I will drop the Coverity patches from this patch series: the conflation of Coverity fixes with the builtin difftool was a mistake, and I will thereby address that mistake.

Ciao, Johannes