public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Th.R.Klein" <Th.R.Klein@web.de>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sources.redhat.com
Subject: Re: [RFC] syntax highlighting
Date: Thu, 25 Aug 2005 17:49:00 -0000	[thread overview]
Message-ID: <430E0651.2040207@web.de> (raw)
In-Reply-To: <430B8791.2070909@redhat.com>

Hi,

Keith Seitz wrote:
> Barring that, there is one more hurdle to overcome: copyright. Unlike 
> most of the patches that I see here, this patch definitely is not even 
> remotely trivial. So we need to get you (and your company if involved) 
> to sign an assignment. The problem is, that assignment is to Red Hat, 
> not the FSF, since Insight is officially owned (albeit carelessly) by 
> Red Hat.

Sorry but I do not understand where I've done something that violates 
the existing copyright.
The file header includes something like this:
...
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License (GPL) as published by
the Free Software Foundation; either version 2 of the License, or (at
your option) any later version.
...

As far as I'm interpreting this, I'm allowed to modify the source e.g. 
by adding the syntax highlighting stuff to it. The copyright remains as 
it was before.
If like that other people can use this modification too, I have either 
to redistribute it myself or I have to ask an existing distributer to do so.
Since Red Hat is the major distributer of Insight it would be great to 
find it there.
Red Hat itself might have a set of rules which kind of modification they 
accept and which they will reject.
If so, it would be nice to this available. So we can produce patches 
that fit.
Maybe Red Hat isn't interested in any kind off patches.
So it would be nice to know this, too.

Again, I haven't understand everything correctly, so it is likely that 
I've got it wrong.

At the current stage I'm a little bit frustrated.

Regards
   Thomas

  parent reply	other threads:[~2005-08-25 17:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 21:12 Th.R.Klein
2005-08-03 21:49 ` Steven Johnson
2005-08-04  6:13 ` Steven Johnson
2005-08-04 10:25   ` Dave Korn
2005-08-23 20:31 ` Keith Seitz
2005-08-23 22:12   ` Steven Johnson
2005-08-24  3:51     ` Christopher Faylor
2005-08-25 17:49   ` Th.R.Klein [this message]
2005-08-25 18:05     ` Jon Beniston
     [not found]     ` <20050825180548.A35334A8054@cgf.cx>
2005-08-25 18:34       ` Christopher Faylor
2005-08-25 19:06         ` Jon Beniston
     [not found]         ` <20050825190632.D45444A8059@cgf.cx>
2005-08-25 19:13           ` Christopher Faylor
2005-08-25 19:59             ` Jon Beniston
     [not found]             ` <20050825195933.041274A805F@cgf.cx>
2005-08-25 20:54               ` Christopher Faylor
2005-08-04 17:35 Th.R.Klein
     [not found] <200508251805.j7PI5q4A015633@mx1.redhat.com>
2005-08-25 18:33 ` Keith Seitz
2005-08-25 21:23   ` Steven Johnson
2005-08-26 10:02     ` Dave Korn
2005-08-26 20:22       ` Christopher Faylor

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=430E0651.2040207@web.de \
    --to=th.r.klein@web.de \
    --cc=insight@sources.redhat.com \
    --cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).