From: Steven Rostedt <rostedt@goodmis.org>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
linux-kernel@vger.kernel.org,
Kalin KOZHUHAROV <kalin@thinrope.net>,
Jesper Juhl <jesper.juhl@gmail.com>, Greg KH <greg@kroah.com>
Subject: Re: Linux kernel development
Date: Mon, 05 Jun 2006 10:58:46 -0400 [thread overview]
Message-ID: <1149519526.16247.3.camel@localhost.localdomain> (raw)
In-Reply-To: <4d8e3fd30606050439j7e299655hf9967678e8739698@mail.gmail.com>
On Mon, 2006-06-05 at 13:39 +0200, Paolo Ciarrocchi wrote:
> > Could you add a README (including contact info, etc), and perhaps a TODO
> > (and a copy of SubmittingPatches, which I assume applies here too?) to the
> > project? A license for the text is required, AFAIU (GPLv2, or one of the
> > Creative Commons licenses perhaps?).
>
> Not and exepert in this area, I think I'll release it under GPL2.
>
> What's the normal approach? Can I just add:
> # This document is distribuited under
> # GNU GENERAL PUBLIC LICENSE
> # Version 2, June 1991
> # http://www.gnu.org/licenses/gpl.txt
>
> To the text?
>
> > [Yup, tangle it up in red tape even before it gets off the ground ;-]
> >
I released by writeup about the rt-mutex-design.txt (currently in -mm
under Documentation) under the "GNU Free Documentation License, Version
1.2".
If you want to read the license it is here:
http://www.gnu.org/copyleft/fdl.html
-- Steve
next prev parent reply other threads:[~2006-06-05 14:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 13:36 Linux kernel development Paolo Ciarrocchi
2006-06-03 18:28 ` Horst von Brand
2006-06-04 10:00 ` Paolo Ciarrocchi
2006-06-04 10:30 ` Paolo Ciarrocchi
2006-06-04 23:05 ` Horst von Brand
2006-06-05 11:39 ` Paolo Ciarrocchi
2006-06-05 14:58 ` Steven Rostedt [this message]
2006-06-05 20:52 ` Paolo Ciarrocchi
2006-06-05 17:38 ` Horst von Brand
2006-06-05 20:51 ` Paolo Ciarrocchi
2006-06-06 19:22 ` Paolo Ciarrocchi
2006-06-06 22:09 ` Horst von Brand
2006-06-07 21:59 ` Paolo Ciarrocchi
-- strict thread matches above, loose matches on Subject: below --
2007-07-16 21:04 Linux Kernel Development Paolo Ciarrocchi
2007-07-16 21:34 ` Michal Piotrowski
2007-07-16 21:37 ` Paolo Ciarrocchi
[not found] <CAK8ka9y1VhMzS0X2GSEg4AQzSMPwOkS3HQxBuX4t-Rp-_OwDow@mail.gmail.com>
2011-08-22 4:51 ` linux kernel development Niloofar Fazlollahi
2011-08-22 4:53 ` Américo Wang
2012-09-09 3:15 Linux Kernel Development Kaushal Shriyan
2012-09-09 3:32 ` Alexandru Juncu
2012-09-09 9:16 ` Kaushal Shriyan
2012-09-09 9:45 ` brliv
2012-09-09 10:20 ` Daniel Baluta
2012-09-09 10:58 ` brliv
2012-09-09 11:54 ` Anuz Pratap Singh Tomar
2012-09-09 10:36 ` Robert P. J. Day
2012-09-09 13:14 ` Davidlohr Bueso
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=1149519526.16247.3.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=greg@kroah.com \
--cc=jesper.juhl@gmail.com \
--cc=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=vonbrand@inf.utfsm.cl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.