public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	Andre Hedrick <andre@linux-ide.org>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Martin Dalecki <dalecki@evision-ventures.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] New driver for Artop [Acard] controllers.
Date: Sun, 26 May 2002 14:48:20 +0200	[thread overview]
Message-ID: <20020526144820.A17158@ucw.cz> (raw)
In-Reply-To: <20020526130547.A16548@ucw.cz> <Pine.LNX.4.44.0205261334250.11662-100000@sharra.ivimey.org>

On Sun, May 26, 2002 at 01:42:51PM +0100, Ruth Ivimey-Cook wrote:

> On Sun, 26 May 2002, Vojtech Pavlik wrote:
> >On Fri, May 24, 2002 at 10:07:36PM -0700, Andre Hedrick wrote:
> >> Where do you get off delete copyrights?
> >> GPL permits changing it does not give you the right to steal, lie, cheat,
> >> defraud, other peoples work.  However I should not expect anything of
> >> honor from a person of your high morals.  I know you want to rewrite the
> >> past to make it so I and other never existed, but you are pathetic.
> >
> >I don't delete copyrights, where applicable. However, in this case, none
> >of the original code stayed, not a single line - I first wrote a spec
> >based on the old driver and then wrote a new driver from scratch based
> >on that spec. So, you really don't have a copyright on the new Artop
> >driver, sorry.
> 
> Vojtech,
> 
> It would be a lot better if you had acknowledged the prior input of the
> original writers in the source; I accept that if you write a new driver you
> are entitled to claim (C) on it, but to acknowledge the source of the
> specification would have been much fairer to the others whose hard work you
> have used.

Yes, I agree. That's why there is:

 *  Based on the work of:
 *     Andre Hedrick

in the new driver.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-05-26 12:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-24 14:29 [patch] New driver for Artop [Acard] controllers Bartlomiej Zolnierkiewicz
2002-05-24 13:33 ` Martin Dalecki
2002-05-24 14:50 ` Vojtech Pavlik
2002-05-24 14:07   ` Martin Dalecki
2002-05-24 15:17     ` Vojtech Pavlik
2002-05-24 15:29 ` Vojtech Pavlik
2002-05-24 15:57   ` Vojtech Pavlik
2002-05-25  5:07   ` Andre Hedrick
2002-05-26  9:50     ` Andre Hedrick
2002-05-26 11:08       ` Vojtech Pavlik
2002-05-26 11:05     ` Vojtech Pavlik
2002-05-26 12:42       ` Ruth Ivimey-Cook
2002-05-26 12:48         ` Vojtech Pavlik [this message]
2002-05-26 23:08       ` Andre Hedrick
2002-05-27  0:42         ` Alan Cox
2002-05-27  0:17           ` Andre Hedrick
2002-05-28 14:09             ` Rob Landley
2002-05-29  8:15               ` Vojtech Pavlik
2002-05-27  3:57           ` Copyright Violation (Re: [patch] New driver for Artop [Acard] controllers.) Andre Hedrick
2002-05-27 15:04             ` Pavel Machek
2002-05-27 14:58         ` [patch] New driver for Artop [Acard] controllers Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2002-05-24 13:46 Vojtech Pavlik

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=20020526144820.A17158@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=Ruth.Ivimey-Cook@ivimey.org \
    --cc=andre@linux-ide.org \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    /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