public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: "Brown, Len" <len.brown@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Alexey Starikovskiy <aystarik@gmail.com>
Subject: Re: Documentation - How to debug ACPI Problems
Date: Tue, 14 Aug 2007 18:49:26 +0200	[thread overview]
Message-ID: <1187110166.8780.522.camel@queen.suse.de> (raw)
In-Reply-To: <200708141140.02233.lenb@kernel.org>

On Tue, 2007-08-14 at 11:40 -0400, Len Brown wrote:
> > +Thomas Renninger <trenn@suse.de>, 2007
> > +Copyright (C) 2007 SUSE Linux GmbH
> 
> While it seems to be generally customary to identify the authors of Documentation
> files, it doesn't seem to be customary for them to assert a copyright.
> Is this really necessary?  My concern is that it could discourage contributors
> for user or changing the text in any way they see fit.
> 
> can anybody offer guidance on this?
> 

I am no license expert, but if you do a:
grep Copyright Documentation/ -r
you see hundreds of Copyrights clauses..., everything in kernel is under
GPL anyway and AFAIK the Copyright is just the explicit statement that
the Author implicitly has anyway...
I don't care that much whether you exactly take this one.
You still might want to take your documentation (I didn't know that you
already set up this one on your ftp account). You still might want to
merge parts of mine if it's appropriate, add a "thanks for input" or
not, at least people have something to read at the end...

Thanks,

   Thomas


  reply	other threads:[~2007-08-14 16:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 14:26 Documentation - How to debug ACPI Problems Thomas Renninger
2004-01-02 22:32 ` Zhang Rui
2007-06-06 14:59 ` Jesper Juhl
2007-06-11 16:28   ` Thomas Renninger
2007-06-18  4:12     ` Len Brown
2007-06-18 11:18       ` Thomas Renninger
2007-08-14 15:25         ` Len Brown
2007-08-14 15:25     ` Len Brown
2007-08-14 15:40     ` Len Brown
2007-08-14 16:49       ` Thomas Renninger [this message]
2007-08-14 16:50       ` Henrique de Moraes Holschuh
2007-08-14 17:33       ` Alan Cox
2007-08-14 18:03       ` Valdis.Kletnieks
2007-06-06 15:52 ` Alexey Starikovskiy

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=1187110166.8780.522.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=aystarik@gmail.com \
    --cc=jesper.juhl@gmail.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.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