From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261185AbVFCImy (ORCPT ); Fri, 3 Jun 2005 04:42:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261186AbVFCImy (ORCPT ); Fri, 3 Jun 2005 04:42:54 -0400 Received: from 200.201.203.62.cust.bluewin.ch ([62.203.201.200]:43339 "EHLO kestrel.twibright.com") by vger.kernel.org with ESMTP id S261185AbVFCImx (ORCPT ); Fri, 3 Jun 2005 04:42:53 -0400 Date: Fri, 3 Jun 2005 10:42:50 +0200 From: Karel Kulhavy To: linux-kernel@vger.kernel.org Subject: CorAccess promises to comply with GPL Message-ID: <20050603084250.GA27017@kestrel> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Orientation: Gay User-Agent: Mutt/1.5.8i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hello After examining CorAccess' product package and becoming convinced they do not comply to GPL, I did a mail conversation with them with this result: "Thank you for bringing this matter to our attention. After reviewing license materials that may have been included with certain products, it appears that while license information for commercially licensed components may have been included, license information for GPL binaries accompanying our product may have been inadvertently left out in some cases. [...] We will update applicable documentation materials to ensure that appropriate GPL language is included and release the new doc kits along with our next production software release." -- Michael Menard, CorAccess Systems, 21 May 2005 (I first mistakenly put it into mouth of Mr. Slawson in a reply in GPL violations thread, because Mr. Menard sent the message via Mr. Slawson's e-mail) CL<