From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Ian Sheldon <is+guile@kaidea.freeserve.co.uk>, bug-guile@gnu.org
Subject: Re: [PATCH] posix.texi: added additional examples
Date: 03 Apr 2002 20:29:57 +0200 [thread overview]
Message-ID: <87k7rotz2x.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3lmcoibnu.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> I don't know. It's not huge, but it is rather longer than the `about
> 10 lines' guideline that I've heard mentioned before.
>
> Marius, can you advise?
Hmm, well, I'm no expert on this but here are some thoughts (with a
conclusion., even :).
The FSF requires copyright assignments to guard against the case that
someone contributes something that he is not allowed to contribute,
and we might be forced to remove the contributions again.
So I tend to see this as a risk assessment, more or less. How high is
the risk that the contribution will be revoked? How much damage will
it cause?
In this case, the risk is very low, and the damage is very small. So,
in my view, it is OK to include the patch without 'the papers'.
However, it can't hurt to ask the contributor anyway (like Rob did).
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2002-04-03 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 17:55 [PATCH] posix.texi: added additional examples Ian Sheldon
2002-03-18 20:39 ` Neil Jerram
2002-03-18 23:16 ` Ian Sheldon
2002-03-19 19:45 ` Neil Jerram
2002-04-02 1:14 ` Rob Browning
2002-04-03 18:29 ` Marius Vollmer [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=87k7rotz2x.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@gnu.org \
--cc=is+guile@kaidea.freeserve.co.uk \
/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).