From: "Benn Newman" <newmanbe@sdf.lonestar.org>
To: 9fans@cse.psu.edu
Subject: [9fans] LPL Section 3C
Date: Sat, 15 Jul 2006 10:08:04 -0500 [thread overview]
Message-ID: <39010.69.21.205.10.1152976084.squirrel@69.21.205.10> (raw)
The Lucent Public License Version 1.02, in relevant part, states:
``In addition, each Contributor must identify itself as the originator of
its Contribution in a manner that reasonably allows subsequent Recipients
to identify the originator of the Contribution. Also, each Contributor
must agree that the additions and/or changes are intended to be a
Contribution. Once a Contribution is contributed, it may not thereafter be
revoked.''
I submited two patches (doc-man-1-patch-email and doc-man-1-fedex-new) but
I am not sure if I am complying with this paragraph. That could be fixed
by adding ``.\" Benjamin T. D. Newman contributed/is the original
contributor to/of this man page'' or something like that, but I have not
see that done anywhere. Should I have done that? Until the patches get
looked at (more specificaly, the email files chmod-ed o-rw) one would be
able to tell who sent the patch (well, not really because it is world
writable.)
--
Benn Newman
next reply other threads:[~2006-07-15 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 15:08 Benn Newman [this message]
2006-07-15 16:53 ` Eric Smith
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39010.69.21.205.10.1152976084.squirrel@69.21.205.10 \
--to=newmanbe@sdf.lonestar.org \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).