From: Jesper Juhl <jesper.juhl@gmail.com>
To: Manfred Gruber <m.gruber@tirol.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Misleading information on linuxdevices.com
Date: Mon, 12 Dec 2005 19:21:37 +0100 [thread overview]
Message-ID: <9a8748490512121021h14a652cdqbc6c53d8a0f4dd3b@mail.gmail.com> (raw)
In-Reply-To: <200512121844.34832.m.gruber@tirol.com>
On 12/12/05, Manfred Gruber <m.gruber@tirol.com> wrote:
> Hi,
>
> as some of you might have noticed, there was an announcement of our
> company on http://www.linuxdevices.com/news/NS9959272388.html
>
> The text is misleading as it speaks about a "propietary" kernel, which
> is completely wrong.
>
Well, your own website also says it proprietary. Quoting the page you
refer to below:
"Contec are now offering a proprietary adaptation of Real Time Linux
for their successful business card sized ARM-9 CPU Modules."
> We run Ingo Molnars rt-preemption patch with modifications for our
> custom board done by Thomas Gleixner and us.
>
> The source code is of course available under the GPL. See also the
> information on our homepage:
> http://www.contec.at/78+M52087573ab0.0.html
>
Where exactely is the source code? I can't seem to find it...
> We don't know where in the information chain from the development team
> via the marketing team to linuxdevices this happened, but we want to
> correct any wrong impression about our company. Sorry.
>
Perhaps you should start by fixing the text on your own homepage and
provide a prominent link to the source code :)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-12-12 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 17:44 Manfred Gruber
2005-12-12 18:21 ` Jesper Juhl [this message]
2005-12-12 18:57 ` Manfred Gruber
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=9a8748490512121021h14a652cdqbc6c53d8a0f4dd3b@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.gruber@tirol.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®