[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Fix to bug #22537: Support RFC 2231, at least for Content

From: Micah Cowan
Subject: Re: [Bug-wget] Fix to bug #22537: Support RFC 2231, at least for Content-Disposition
Date: Wed, 23 Sep 2009 16:41:47 -0700
User-agent: Thunderbird (X11/20090817)

Hash: SHA1

Arvind Jamuna Dixit wrote:
> Hi,
> This patch to wget enables wget to parse Content-Disposition header in
> conformance to RFC 2231.
> I have attached the patch file with this mail.

Your patch looks fine to me, Arvind. I've just rediscovered a patch that
would combine well with it: see

In order for me to include your contributions in Wget, you'll need to
sign a disclaimer with the Free Software Foundation. If you're employed
to write software at a company, your employer may need to sign something
as well.

If you're planning on continuing to contribute to Wget in the future,
the recommended option is to assign copyright over all past and future
changes you make to Wget, to the Free Software Foundation (I've done
this myself). I've attached the request-form corresponding to this.

Otherwise, you can choose to assign copyright over just the specific
changes you've made, in which case you'll have to sign papers again for
any future changes you make (but not bugfixes to this set of changes).
Or you can sign a disclaimer granting permission to use your changes,
but not assigning copyright. If you'd prefer either of these choices,
please let me know, and I'll send you the forms for those instead.

If you decide you'd like to assign for past and future changes, please
fill in the attached form and send it along to address@hidden; they'll
then send you the appropriate paperwork.

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
Maintainer of GNU Wget and GNU Teseq
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

Please email the following information to address@hidden, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.

[What is the name of the program or package you're contributing to?]

[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]

[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]

[For the copyright registration, what country are you a citizen of?]

[What year were you born?]

[Please write your email address here.]

[Please write your postal address here.]

[Which files have you changed so far, and which new files have you written
so far?]

Attachment: request-assign.future.sig
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]