unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Clinton Ebadi <clinton@unknownlamer.org>
Cc: bug-guile@gnu.org
Subject: Re: Weak Vectors Patch
Date: Sat, 17 Apr 2010 22:48:40 +0200	[thread overview]
Message-ID: <87d3xx6c0n.fsf@gnu.org> (raw)
In-Reply-To: <874ojarkoe.fsf@rvannith.home.unknownlamer.org> (Clinton Ebadi's message of "Sat, 17 Apr 2010 14:36:01 -0400")

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

Hi!

Clinton Ebadi <clinton@unknownlamer.org> writes:

> ludo@gnu.org (Ludovic Courtès) writes:

[...]

>> The patch looks good to me, modulo a few things:
>>
>>   - Could you make it 3 (or 4?) different patches, each with a test case
>>     showing what is being fixed?
>>
>>   - If that’s fine with you, you’ll need to assign copyright to the
>>     FSF.  We can arrange this off-list.
>
> I have attached a series of three patches with reformatted GNU style
> commit logs and the gnu coding style violations fixed.

Cool, thanks!

> I talked to wingo, and he suggested that (equal? WEAK-VECTOR VECTOR) =>
> #f;

Hmm what’s the motivation?  It seems more intuitive to me to have, e.g.,

  (equal? (make-vector 3 4) (make-weak-vector 3 4))
  => #t

> How do you want to handle copyright assignment?

The usual way.  ;-)

So, would you be willing to assign the copyright to the Free Software
Foundation, so that we could install it in Guile?

If so, please send the form below to assign@gnu.org.  They’ll then send
you the actual copyright assignment form by snail mail, which you’ll
have to sign and send back, after which we can integrate these and
future changes by you in Guile.

Thanks!

Ludo’.


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 #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-04-17 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 17:18 Weak Vectors Patch Clinton Ebadi
2010-04-05 17:03 ` Ludovic Courtès
2010-04-05 17:26   ` Andy Wingo
2010-04-17 18:36   ` Clinton Ebadi
2010-04-17 20:48     ` Ludovic Courtès [this message]
2010-04-18 11:48       ` 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=87d3xx6c0n.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@gnu.org \
    --cc=clinton@unknownlamer.org \
    /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).