From: Andy Wingo <wingo@pobox.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: ludo@gnu.org, 10109-done@debbugs.gnu.org
Subject: bug#10109: [PATCH] (web http): list-style headers do not validate
Date: Wed, 23 Nov 2011 21:25:48 +0100 [thread overview]
Message-ID: <87ehwymvqr.fsf@pobox.com> (raw)
In-Reply-To: <CAN3veRdguxwk0JKQDU=+KYUOKAJZuaXMHYwxxy03Zw=pBqbt_w@mail.gmail.com> (Daniel Hartwig's message of "Wed, 23 Nov 2011 02:18:36 +0800")
On Tue 22 Nov 2011 19:18, Daniel Hartwig <mandyke@gmail.com> writes:
> Many of the list-style headers from (web http) do not validate
> correctly. The test suite only checks that the header's parse and
> does not test the associated validators.
I applied both of your patches. Thank you very much!
In the future, please make your patches as separate git commits in your
repository. Then do `git format-patch origin/stable-2.0..HEAD'. Then
attach the generated files to a mail. The advantage is that I don't
have to cut and paste your commit log, and I don't have to make special
effort to ensure that you are listed as the author in the commits.
Also, your first patch is probably at the limit of how big a patch we
can accept without getting you to assign copyright to the FSF. If you
think you will send more patches in the future, it's probably a good
idea to start that process, if you are OK with that. Email me privately
and I'll tell you how to do that. Note that GNU has recently entered
the 20th century ;) by sending the forms via PDF. You can submit them
electronically too, but only if you are a US resident. Anyway, send me
an email if you are interested.
Thanks again for the patches!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-11-23 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 18:18 bug#10109: [PATCH] (web http): list-style headers do not validate Daniel Hartwig
2011-11-23 20:25 ` Andy Wingo [this message]
2011-11-27 15:11 ` Daniel Hartwig
2011-12-22 13:21 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehwymvqr.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10109-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mandyke@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 read-only IMAP folder(s) and NNTP newsgroup(s).