From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: backtrace(3) in Cygwin
Date: Fri, 20 Mar 2015 19:15:00 -0000 [thread overview]
Message-ID: <20150320191524.GK2368@calimero.vinschen.de> (raw)
In-Reply-To: <20150317085708.GA20267@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Hi David,
On Mar 17 09:57, Corinna Vinschen wrote:
> On Mar 16 22:21, David Stacey wrote:
> > On 16/03/15 10:07, Corinna Vinschen wrote:
> > >Unfortunately there are some preliminaries before I can take a closer
> > >look, namely the copyright assignment we need from everybody who's
> > >providing more than just trivial patches to Cygwin, see
> > >https://cygwin.com/contrib.html, the "Before you get started" section.
> > >Fill out https://cygwin.com/assign.txt and send it to the address given
> > >in the pamphlet. If you're writing code for Cygwin only in your spare
> > >time, forget the part about your employer.
> >
> > I'm hoping that this won't be a problem. I'm more than happy to assign my
> > own copyright to Red Hat. My employer has no claim to work I do in my own
> > time on my own equipment. However, Cygwin might be a grey area, as we use
> > Cygwin extensively in our development work. So I've already asked my
> > employer to sign the copyright and patent waiver. Assuming this is signed,
> > I'll send both parts together.
> >
> > So let's proceed assuming that this is going to happen.
FYI, as I just wrote on the cygwin ML, legal gave us permission to
collect the copyright assignments as PDF. Print it, sign it, scan as
PDF, and send to ges-info AT redhat DOT com. That's all from now on!
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-20 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 19:52 David Stacey
2015-03-16 10:07 ` Corinna Vinschen
2015-03-16 22:22 ` David Stacey
2015-03-17 8:57 ` Corinna Vinschen
2015-03-20 19:15 ` Corinna Vinschen [this message]
2015-03-20 23:59 ` David Stacey
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=20150320191524.GK2368@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@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).