public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dalibor Topic <robilad@kaffe.org>
To: tromey@redhat.com
Cc: Audrius Meskauskas <audriusa@bluewin.ch>,
	Mauve discuss <mauve-discuss@sourceware.org>
Subject: Re: Re:Mauve liscense:GPL 3?
Date: Tue, 21 Feb 2006 19:53:00 -0000	[thread overview]
Message-ID: <1140551604.14397.2.camel@amy.domain.wg> (raw)
In-Reply-To: <17402.21244.605800.963673@localhost.localdomain>

On Tue, 2006-02-21 at 00:38 +0100, Tom Tromey wrote:
> >>>>> "Dalibor" == Dalibor Topic <robilad@kaffe.org> writes:
> 
> Dalibor> On Fri, 2006-02-17 at 09:44 +0100, Audrius Meskauskas wrote:
> >> Stupid idea this morning, but if the GPL 3 would be Apache compatible, 
> >> maybe we could just show more intiative and merge the Java tests from 
> >> THEY testing project? All we need is the JUnit adapter to Mauve that it 
> >> is for sure possible to write. I was suggesting this idea long time ago.
> 
> Dalibor> Sure, next year when the GPL3 is released, we could do that.
> 
> I'm not sure we even need that.  Couldn't we have a single harness to
> run both sets of tests and distribute the result under a mixed
> license?

Uh ... sort of. You can have a harness that is both a) GPL-compatibly
licensed and b) something-else-compatibly licensed, and distribute it as
part of Mauve. GPL+linking exception would work well for anything, I
think.

cheers,
dalibor topic

      reply	other threads:[~2006-02-21 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17  8:45 Audrius Meskauskas
2006-02-18 16:57 ` Dalibor Topic
2006-02-20 23:53   ` Tom Tromey
2006-02-21 19:53     ` Dalibor Topic [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=1140551604.14397.2.camel@amy.domain.wg \
    --to=robilad@kaffe.org \
    --cc=audriusa@bluewin.ch \
    --cc=mauve-discuss@sourceware.org \
    --cc=tromey@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).