-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-01-06 01:01, Russ Allbery wrote:
Niels Thykier ni...@thykier.net writes:
I am considering to just make the switch to use Email::Valid. I have
attached a patch that makes the switch and introduces a regression test
to catch the
Niels Thykier ni...@thykier.net writes:
I rechecked the code and it is not a problem. Email::Valid does indeed
reject these names, but it is currently only applied to check the
m...@debian.org part. The names are still checked by the old
home-made regex approach.
Nevertheless I have added
Niels Thykier ni...@thykier.net writes:
I am considering to just make the switch to use Email::Valid. I have
attached a patch that makes the switch and introduces a regression test
to catch the particular issue in #602619.
The only caveat with using Email::Valid is that Debian Policy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-01-06 01:01, Russ Allbery wrote:
Niels Thykier ni...@thykier.net writes:
I am considering to just make the switch to use Email::Valid. I have
attached a patch that makes the switch and introduces a regression test
to catch the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
I am considering to just make the switch to use Email::Valid. I have
attached a patch that makes the switch and introduces a regression test
to catch the particular issue in #602619.
~Niels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10
Package: lintian
Version: 2.4.3
Severity: wishlist
Tags: patch
Please,
It would be really nice if Lintian could catch serious bug like #602619.
The naive attached patch permit to do so, but there must be nicer.
Regards
David
-- System Information:
Debian Release: squeeze/sid
APT prefers
6 matches
Mail list logo
