From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Derrick Stolee <stolee@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Git Test Coverage Report (v2.28.0-rc0)
Date: Fri, 10 Jul 2020 02:55:37 +0000 [thread overview]
Message-ID: <20200710025537.GJ9782@camp.crustytoothpaste.net> (raw)
In-Reply-To: <fcc3f6da-2b6a-239d-c865-64378ba31510@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On 2020-07-10 at 02:12:26, Derrick Stolee wrote:
> brian m. carlson ac093d07 remote-curl: detect algorithm for dumb HTTP by size
I've noticed that I appear several times on this list. As is probably
apparent, most of this is covered by the SHA-256 work, and will be
covered appropriately by it when run with an appropriate test option.
That won't fix things for 2.28, but it should cover 2.29.
The relevant series has hit my MX, if not the list, and if there are
still additional things outstanding that are uncovered, I'll send
follow-up patches to cover anything left over.
--
brian m. carlson: Houston, Texas, US
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2020-07-10 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 2:12 Git Test Coverage Report (v2.28.0-rc0) Derrick Stolee
2020-07-10 2:55 ` brian m. carlson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200710025537.GJ9782@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=stolee@gmail.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.
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 NNTP newsgroup(s).