From: Corinna Vinschen <vinschen@redhat.com>
To: cygwin-announce@cygwin.com
Subject: New procedure for code contributions to the Cygwin sources
Date: Thu, 23 Jun 2016 18:35:00 -0000 [thread overview]
Message-ID: <20160623183415.GN15373@calimero.vinschen.de> (raw)
Hi folks,
as mentioned in https://cygwin.com/ml/cygwin-announce/2016-06/msg00048.html
the procedure for contributions to the Cygwin sources has been much
simplified.
If you already have the former Cygwin Copyright Assignment signed and
submitted, you're all set.
Otherwise, just make a public statement that you provide your patches to
the Cygwin sources under the 2-clause BSD license.
You can do that, for instance, with your first patch submission. After
your first patch has been approved and applied, your name and email
address will be added to the new winsup/CONTRIBUTORS file. That's all.
For the wording of the 2-clause BSD license, see the winsup/CONTRIBUTORS
file.
Contributions to the newlib sources are still exempt from this procedure.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
reply other threads:[~2016-06-23 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160623183415.GN15373@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=cygwin-announce@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).