Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Fri, 29 Jun 2007, Russ Allbery wrote:
>> According to RFC 2396, the list of characters reserved, banned, or
>> disrecommended for URIs are:
>>
>> ; / ? : @ & = + $ , < > # % " { } | \ ^ [ ] `
>>
>> and space. The safest thing to do would be t
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Thu, 28 Jun 2007, Russ Allbery wrote:
>> Well, he extracts everything between <>, but I believe we still lose
>> if, for instance, there's a # in the e-mail address (which is an
>> entirely valid RFC 2822 character). I'm a little worried about +,
>
Raphael Geissert <[EMAIL PROTECTED]> writes:
> Package: qa.debian.org
> Tags: patch
> Followup-For: Bug #373218
> I just wrote a patch for this problem. The best solution I found it to
> drop the current naming convention of the lintian reports and use the
> maintainer login (the same way most o
Package: qa.debian.org
Tags: patch
Followup-For: Bug #373218
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just wrote a patch for this problem.
The best solution I found it to drop the current naming convention of the
lintian reports and use the
maintainer login (the same way most of the othe
4 matches
Mail list logo
