From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Verify Size of Objcode Headers
Date: Sun, 20 Jun 2010 22:30:58 +0200 [thread overview]
Message-ID: <m3eig1cupp.fsf@pobox.com> (raw)
In-Reply-To: <AANLkTin3t5ss9MnTEKwx2Am18kQ_IsUZpeNtZK5CQTzB@mail.gmail.com> (Noah Lavine's message of "Sun, 20 Jun 2010 15:44:58 -0400")
On Sun 20 Jun 2010 21:44, Noah Lavine <noah.b.lavine@gmail.com> writes:
> Add static checks to make sure that the statically-generated object code
> headers in continuations.c, control.c, foreign.c, gsubr.c and smob.c are the
> same length as the struct scm_objcode data type in objcodes.h.
I'd be happy to apply these. Would you be willing to assign copyright
for your changes to Guile to the FSF? Reply privately and we can get the
paperwork in motion.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-06-20 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 19:44 [PATCH] Verify Size of Objcode Headers Noah Lavine
2010-06-20 20:30 ` Andy Wingo [this message]
2010-06-20 21:22 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2010-06-20 23:59 Noah Lavine
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=m3eig1cupp.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@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).