unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Scott McPeak <smcpeak@coverity.com>
Cc: bug-guile@gnu.org
Subject: Re: windows sockets vs. file descriptors bugs in Guile
Date: Sat, 27 Mar 2010 22:24:09 +0000	[thread overview]
Message-ID: <871vf5h08m.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87634hh121.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 27 Mar 2010 22:06:30 +0000")

[-- Attachment #1: Type: text/plain, Size: 579 bytes --]

Neil Jerram <neil@ossau.uklinux.net> writes:

> Most of that patch is yours, so we will need a copyright assignment from
> you.  Please say if you need help finding and submitting the papers for
> that (or if it's a problem).

I'm sorry, on rereading your previous email I see that you already said
"let me know what I need to do".  So here's the answer.

If you think that you might contribute more Guile patches in future, you
could sign an assignment that will cover both this and any future
contributions.  In this case please see the attached file
"request-assign.future".


[-- Attachment #2: request-assign.future --]
[-- Type: text/plain, Size: 971 bytes --]

Please email the following information to assign@gnu.org, 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.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[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 #3: Type: text/plain, Size: 265 bytes --]


Alternatively, to cover just the contributions that you already have
pending (i.e. including also the sleep and scm_copy_file patches), there
is a simpler copyright disclaimer.  If you'd prefer this route, please
see the attached file "request-disclaim.changes".


[-- Attachment #4: request-disclaim.changes --]
[-- Type: text/plain, Size: 1327 bytes --]

Please email the following information to assign@gnu.org, and we will
send you the disclaimer form for your changes.  This form is preferred
when your changes are small, they do not add any nontrivial new
files, and you are finished making them (aside perhaps from small bug
fixes).

If you would like to make further contributions to the same package,
and you would like to avoid the need to sign more papers when you
contribute them, you have another option: to sign a copyright
assignment covering your future changes.  If that is what you want to
do, please tell the maintainer you would prefer to sign an assignment
of past and future changes.


Please use your full legal name (in ASCII characters) as the subject
line of the message.
-----------------------------------------------------------------------
REQUEST: SEND DISCLAIMER FORM

[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?]


[Please write your email address here.]


[Please write your snail address here.]





[Please list the files involved, or give a brief description of the changes
being disclaimed.]







[-- Attachment #5: Type: text/plain, Size: 25 bytes --]


Many thanks!

     Neil

      reply	other threads:[~2010-03-27 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  4:15 windows sockets vs. file descriptors bugs in Guile Scott McPeak
2009-10-01  7:43 ` Ludovic Courtès
2009-10-02 22:33 ` Neil Jerram
2009-10-03  0:03   ` Scott McPeak
2010-03-27 22:06     ` Neil Jerram
2010-03-27 22:24       ` Neil Jerram [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

  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=871vf5h08m.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=bug-guile@gnu.org \
    --cc=smcpeak@coverity.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).