From: Junio C Hamano <gitster@pobox.com>
To: "Csókás Bence" <csokas.bence@prolan.hu>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH v2] git-send-email: Use sanitized address when reading mbox body
Date: Thu, 27 Jun 2024 08:09:02 -0700 [thread overview]
Message-ID: <xmqq34oywhgx.fsf@gitster.g> (raw)
In-Reply-To: <f245c5e8-b986-49f1-91fe-7e24593e8e85@prolan.hu> ("Csókás Bence"'s message of "Thu, 27 Jun 2024 10:37:06 +0200")
Csókás Bence <csokas.bence@prolan.hu> writes:
> Valid addresses are already tested by former tests. I don't
> immediately see any tests that would cover non-Cc, non-*-by and
> non-email-address tags, so I might add them; should they be a separate
> testcase or part of this one? Or maybe even a separate patch?
The tests you added has only malformed addresses on trailers, and
adding a few trailers with valid addresses *and* string that does
not look like an address at all, would be a minimal fix that makes
the test complete.
It makes it clear that the point of the new test is about strings
found on trailers (that are dealt differently from addresses taken
from other places) are handled appropriately, checked how they are
shown to the MTA (with the comparison !address! output from
fake.sendmail script) and how their additions are logged in the
verbose output (with the pattern match with "^(body) Adding cc:
..."). Checking that totally irrelevant ones (e.g. bugId) are not
even used as addresses, strings meant as addresses but malformed are
used after correction, and well-formed addresses are used as-is,
would form a complete set of observable behaviour from this feature.
Thanks.
prev parent reply other threads:[~2024-06-27 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 13:24 [PATCH v2] git-send-email: Use sanitized address when reading mbox body Csókás, Bence
2024-06-26 17:28 ` Junio C Hamano
2024-06-27 8:37 ` Csókás Bence
2024-06-27 15:09 ` Junio C Hamano [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=xmqq34oywhgx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=csokas.bence@prolan.hu \
--cc=git@vger.kernel.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.