All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Seitz <s.seitz@netz-haut.de>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: harry <harry@hebutterworth.freeserve.co.uk>,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH][1/17] USB virt 2.6 split driver---xenidc platform
Date: Mon, 21 Nov 2005 22:03:53 +0100	[thread overview]
Message-ID: <43823639.7010101@netz-haut.de> (raw)
In-Reply-To: <20051121201049.GA22728@granada.merseine.nu>

Muli Ben-Yehuda schrieb:

>>+/* This program is free software; you can redistribute it and/or modify it   */
>>+/* under the terms of the GNU General Public License as published by the     */
>>+/* Free Software Foundation; either version 2 of the License, or (at your    */
>>+/* option) any later version.
>>    
>>
>*/
>
>Do we really need the GPL in every source file?
>  
>

Hi,

i'm not in the position to criticise your code here, but from my single
point of view, it does make
sense to include the GPL or whatever license into every single source file.
since every single file _could_ be used in other projects, this makes it
very clear to every developer
how to handle the 'borrowed' code.
at some projects i was always happy to find some GPL'ed or LGPL'ed code
with somewhat trivial but
timeconsumpting functions e.g. multibyte_aes256_crypt . if you're
looking for some special function,
there's surely no library for inclusion available :)
anyway, a license note in your source files doesn't harm at all. (well,
with some editor you might need
to push the page down button twice...)

greetings

Stephan

  reply	other threads:[~2005-11-21 21:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 13:18 [PATCH][1/17] USB virt 2.6 split driver---xenidc platform harry
2005-11-21 20:10 ` Muli Ben-Yehuda
2005-11-21 21:03   ` Stephan Seitz [this message]
2005-11-21 21:07     ` Muli Ben-Yehuda
2005-11-21 21:21   ` Harry Butterworth
2005-11-22 10:51     ` Muli Ben-Yehuda
2005-11-22 11:05       ` harry
2005-11-22 15:05         ` Mark Williamson
2005-11-22  0:10   ` Anthony Liguori

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=43823639.7010101@netz-haut.de \
    --to=s.seitz@netz-haut.de \
    --cc=harry@hebutterworth.freeserve.co.uk \
    --cc=mulix@mulix.org \
    --cc=xen-devel@lists.xensource.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 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.