mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Markus Rechberger" <mrechberger@gmail.com>
To: "linux@horizon.com" <linux@horizon.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] New, yet unsupported USB-Ethernet adaptor
Date: Mon, 8 May 2006 17:51:38 +0200	[thread overview]
Message-ID: <d9def9db0605080851k318a6b7x9f3f5103cabe7cc8@mail.gmail.com> (raw)
In-Reply-To: <20060506232311.7353.qmail@science.horizon.com>

Hi,

is anyone already on that issue?
Delock will send me a testdevice, I'll migrate the code to the new
usbnet framework then. Fixing the copyrights shouldn't be such a
problem there :)

Markus

On 6 May 2006 19:23:11 -0400, linux@horizon.com <linux@horizon.com> wrote:
> >>> Correct.  He is violating the license in a number of ways, though it
> >>> probably isn't totally intentional.
> >>
> >> Removing copyright and licence statements can't have been anything BUT
> >> intentional.
> >>
> >> That's really a basic rule, pretty much a "programming 101" thing.  You
> >> know, like "test your code", "don't remove other folks' copyrights",
> >> "don't try to change the licence on code copyrighted by someone else".
>
> That's programming 101 in a litigous country.  Some people are lucky
> enough to live in places where the law is treated with the respect
> it deserves.
>
> > Well, I suspect that poor soul did not know what (s)he was doing. They
> > are clearly trying to do the right thing... just paste back original
> > copyrights and be done with it.
>
> > No need to pull them into the loop, I'd say. What they done is wrong,
> > but we can correct it without their help.
>
> I'm with Pavel.  This was probably done by some underpaid junior coder
> in Bangalore who is utterly innocent of law, much less international law.
>
> The point is, they didn't try to claim it's proprietary and a trade secret.
> Misplacing the credit is very rude, but also easily fixable, especially
> once the duplicate code is properly factored out.
>
> A mention of "you shouldn't do that" is appropriate, but harassing a party
> who's basically being cooperative is unnecessary and counterproductive.
>
> A lot of expensive stonewalling in courts is caused by the fact that
> it's dangerous to admit that you did anything wrong; it has very little
> benefit, and lawyers proceed to just twist it into "and what else *aren't*
> they admitting to?"  Unless you want to encourage that behaviour,
> please don't make their lawyers regret that they let the source code
> out with the incriminating lack-of-comments.  Just fix it and move on.
>
> Save your righteous ire for the hard cases at gpl-violations.org.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


--
Markus Rechberger

  reply	other threads:[~2006-05-08 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-06 23:23 linux
2006-05-08 15:51 ` Markus Rechberger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-02 18:02 Michael Helmling
2006-05-02 22:09 ` [linux-usb-devel] " David Brownell
2006-05-03  5:06   ` Michael Helmling
2006-05-03  5:29     ` David Brownell
2006-05-03 13:28       ` Michael Helmling
2006-05-03 14:44         ` David Hollis
2006-05-03 15:31           ` Andrey Panin
2006-05-03 18:14             ` Michael Helmling
2006-05-03 18:33               ` Pavel Machek
2006-05-03 19:10           ` David Brownell
2006-05-03 19:23             ` David Brownell
2006-05-03 18:31   ` Pavel Machek

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=d9def9db0605080851k318a6b7x9f3f5103cabe7cc8@mail.gmail.com \
    --to=mrechberger@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=linux@horizon.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

all inboxes | Powered by JetHome®