From: Matthew DeVore <matvore@comcast.net>
To: Matthew DeVore <matvore@google.com>
Cc: git@vger.kernel.org, sandals@crustytoothpaste.net,
jeffhost@microsoft.com, l.s.r@web.de, gitster@pobox.com,
spearce@spearce.org, jrn@google.com
Subject: Re: [PATCH v2 0/2] Harden url.c URL-decoding logic
Date: Tue, 4 Jun 2019 14:13:44 -0700 [thread overview]
Message-ID: <20190604211344.GM4641@comcast.net> (raw)
In-Reply-To: <cover.1559670300.git.matvore@google.com>
First message had incorrect recipient list. Re-sending with non-typo'd Jeff's
e-mail address.
Someone also politely reminded me off-band that I should make subsequent
versions of patchsets be respond-to on the cover-letter of v1 of that patchset.
I will do that from next time.
prev parent reply other threads:[~2019-06-04 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 17:57 [PATCH v2 0/2] Harden url.c URL-decoding logic Matthew DeVore
2019-06-04 17:57 ` [PATCH v2 1/2] url: do not read past end of buffer Matthew DeVore
2019-06-04 20:27 ` Junio C Hamano
2019-06-04 17:57 ` [PATCH v2 2/2] url: do not allow %00 to represent NUL in URLs Matthew DeVore
2019-06-04 21:13 ` Matthew DeVore [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=20190604211344.GM4641@comcast.net \
--to=matvore@comcast.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=jrn@google.com \
--cc=l.s.r@web.de \
--cc=matvore@google.com \
--cc=sandals@crustytoothpaste.net \
--cc=spearce@spearce.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.