From: Ramsay Jones <ramsay@ramsayjones.plus.com>
Date: Thu, 24 Jan 2019 19:39:14 GMT
Subject: Re: Git Test Coverage Report (Sat Jan 19)
Message-ID: <5fe36d0a-e7f1-6349-27ed-a6d48a3ba1e3@ramsayjones.plus.com>
In-Reply-To: <7aaec7c8-6cf9-fbd5-fbaf-60b110e2bac7@gmail.com>



On 24/01/2019 19:18, Derrick Stolee wrote:
> On 1/24/2019 1:15 PM, Junio C Hamano wrote:
>> Derrick Stolee <stolee@gmail.com> writes:
>>
>>> Here is today's test coverage report.
>>>
>>> Also, there has been some feedback that it can be hard to manually
>>> match up uncovered lines with names at the bottom of the summary. The
>>> suggestion was to auto-generate an HTML report that could be posted to
>>> a public page and referenced in this mail for those who prefer
>>> that.
>> I wanted to "grep" for lines attributed to certain commits that
>> appear in the list, by filtering lines that begin with enough number
>> of hexdigits, except for those object names, but the attempt failed
>> miserably because of the line wrapping (which probably comes from
>> the assumption that it is OK because the "text/plain; format=flowed"
>> would not care).  If you can keep the long lines (due to the object
>> names and line numbers prefixed to each line) unsplit, it would be
>> more useful to locate and isolate lines.
> This is likely more a problem with my workflow (pasting the report into Thunderbird and sending) than with the content itself.

Have you read Doucmentation/git-format-patch.txt (Thunderbird>
Approach #2 (configuration) - approx. line 487)?

ATB,
Ramsay Jones