From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Adding MSYS functionality to Cygwin
Date: Wed, 19 Jun 2013 20:25:00 -0000 [thread overview]
Message-ID: <20130619192707.GH1620@calimero.vinschen.de> (raw)
In-Reply-To: <CA+sc5mnGC3HeE-+ZsvvuS6VL0ncojtOPP30Ob+WR_yun=vij0Q@mail.gmail.com>
On Jun 19 11:04, Earnie Boyd wrote:
> On Tue, Jun 18, 2013 at 2:40 PM, ÐлекÑей Ðавлов wrote:
> > I want to add MSYS functionality to Cygwin.
>
> One issue with that would be copyright assignment. Alexey has been in
> the MSYS code so someone who hasn't looked would need to implement
> similar functionality.
Only if it becomes part of Cygwin. If we implement the plugin/hook
method, the licensing is no problem. The plugin could certainly
use plain GPLv3+ again.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2013-06-19 19:27 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 18:59 Алексей Павлов
2013-06-18 19:10 ` Christopher Faylor
2013-06-18 19:30 ` Warren Young
2013-06-18 19:31 ` Алексей Павлов
2013-06-18 22:12 ` Warren Young
2013-06-18 22:35 ` Warren Young
2013-06-18 23:51 ` Warren Young
2013-06-19 2:03 ` Christopher Faylor
2013-06-19 7:17 ` Алексей Павлов
2013-06-19 8:15 ` Alexey Pavlov
2013-06-19 11:04 ` Corinna Vinschen
2013-06-19 13:02 ` Alexey Pavlov
2013-06-19 17:31 ` Warren Young
2013-06-19 17:57 ` Christopher Faylor
2013-06-20 3:30 ` Charles Wilson
2013-06-20 13:12 ` Earnie Boyd
2013-06-20 17:13 ` Corinna Vinschen
2013-06-19 13:41 ` Charles Wilson
2013-06-19 18:38 ` Warren Young
2013-06-19 19:27 ` Yaakov (Cygwin/X)
2013-06-20 18:11 ` cygport limitations (was: Adding MSYS functionality to Cygwin) Warren Young
2013-06-20 18:44 ` Corinna Vinschen
2013-06-21 4:41 ` Andrew Schulman
2013-06-21 8:06 ` Corinna Vinschen
2013-06-21 16:55 ` Christopher Faylor
2013-06-21 20:35 ` Andrew Schulman
2013-06-21 21:01 ` Christopher Faylor
2013-06-24 9:13 ` Corinna Vinschen
2013-06-24 11:31 ` Earnie Boyd
2013-06-24 11:56 ` Corinna Vinschen
2013-06-25 11:12 ` Csaba Raduly
2013-06-25 12:06 ` Earnie Boyd
2013-06-21 18:07 ` cygport limitations Warren Young
2013-06-21 18:38 ` Warren Young
2013-06-21 19:31 ` Yaakov (Cygwin/X)
2013-06-24 9:17 ` Corinna Vinschen
2013-06-20 19:11 ` Yaakov (Cygwin/X)
2013-06-21 7:26 ` Warren Young
2013-06-20 22:31 ` David Stacey
2013-06-18 21:22 ` Adding MSYS functionality to Cygwin Christopher Faylor
2013-06-18 21:29 ` Warren Young
2013-06-19 2:05 ` Christopher Faylor
2013-06-19 9:05 ` Corinna Vinschen
2013-06-19 9:29 ` Corinna Vinschen
2013-06-19 17:03 ` Warren Young
2013-06-19 17:36 ` Corinna Vinschen
2013-06-18 21:33 ` Charles Wilson
2013-06-19 2:06 ` Christopher Faylor
2013-06-19 13:59 ` Charles Wilson
2013-06-19 15:56 ` Earnie Boyd
2013-06-19 20:25 ` Corinna Vinschen [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=20130619192707.GH1620@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).