public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Chris Moller <cmoller@redhat.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk@sourceware.org
Subject: Re: Chris' utracer
Date: Fri, 31 Aug 2007 00:38:00 -0000	[thread overview]
Message-ID: <46D762EB.9040509@redhat.com> (raw)
In-Reply-To: <20070830233009.GH22263@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

I just added a copyright notice to each of the files and committed the lot.

cm

Kris Van Hees wrote:
> On Thu, Aug 30, 2007 at 07:14:10PM -0400, Chris Moller wrote:
>   
>> Kris Van Hees wrote:
>>     
>>> After doing a checkout of the frysk-utrace module to haved a look at it, I
>>> notived that it does not have any form of license or copyright statement
>>> listed.  The only hint at a license is in the kernel module license
>>> specification.
>>>
>>> Is that intentional, or oversight?
>>>       
>> It's an oversight, but it's still very much alpha-level code and not
>> intended for general distribution.
>>     
>
> Thanks for clearing that up.  I definitely wasn't thinking about any form of
> distribution or other use beyond frysk.  It just seemed odd to not have any
> copyright or license information on the files, hence the question.  Having
> it in there will avoid any confusion about the code's status in a public
> repository.
>
> 	Cheers,
> 	Kris
>   

-- 
Chris Moller

  Java: the blunt scissors of programming languages.
      -- Dave Thomas



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      reply	other threads:[~2007-08-31  0:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 20:20 Kris Van Hees
2007-08-30 23:15 ` Chris Moller
2007-08-30 23:31   ` Kris Van Hees
2007-08-31  0:38     ` Chris Moller [this message]

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=46D762EB.9040509@redhat.com \
    --to=cmoller@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=kris.van.hees@oracle.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).