From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git Test Coverage Report (Sat Jan 19)
Date: Thu, 24 Jan 2019 14:18:52 -0500 [thread overview]
Message-ID: <7aaec7c8-6cf9-fbd5-fbaf-60b110e2bac7@gmail.com> (raw)
In-Reply-To: <xmqqa7jp53d2.fsf@gitster-ct.c.googlers.com>
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.
If I instead created a text document and sent it with `git send-email`,
then would the line endings work the way you want?
Thanks,
-Stolee
next prev parent reply other threads:[~2019-01-24 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 1:07 Git Test Coverage Report (Sat Jan 19) Derrick Stolee
2019-01-24 18:15 ` Junio C Hamano
2019-01-24 19:18 ` Derrick Stolee [this message]
2019-01-24 19:39 ` Ramsay Jones
2019-01-24 20:56 ` Derrick Stolee
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=7aaec7c8-6cf9-fbd5-fbaf-60b110e2bac7@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).