From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: Necessity for the assignment form
Date: Fri, 20 May 2016 05:46:00 -0000 [thread overview]
Message-ID: <8af86ed5-e1cd-77f4-335b-d192ef3dfe6e@tiscali.co.uk> (raw)
In-Reply-To: <o8xeg8x7e2r.wl-koba@jp.fujitsu.com>
On 20/05/16 01:44, KOBAYASHI Shinji wrote:
> I found a bug and I am willing to submit a patch (under
> winsup/cygwin). But before doing that, I was asked from my employer to
> clarify some points.https://cygwin.com/contrib.html says that the
> assignment form is required "if your change is going to be a
> significant one in terms of the size of your code changes". So the
> questions are:
>
> 1. Who is going to determine if the change is "a significant one"?
> 2. In fact, my patch is just two lines of modifications, so I believe
> that it is not "a significant one". Is it okay to send such a small
> patch without the assignment form?
For Cygwin, the boundary between trivial and substantial is usually
taken as ten lines. A two-line patch would probably be accepted without
an assignment form.
Dave.
--
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
next prev parent reply other threads:[~2016-05-20 5:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 0:45 KOBAYASHI Shinji
2016-05-20 1:22 ` Warren Young
2016-05-20 4:22 ` Invalid tm_zone from localtime() when TZ is not set KOBAYASHI Shinji
2016-05-20 7:09 ` Csaba Raduly
2016-05-20 10:16 ` KOBAYASHI Shinji
2016-05-25 9:28 ` KOBAYASHI Shinji
2016-05-25 10:15 ` Corinna Vinschen
2016-05-26 11:03 ` Hans-Bernhard Bröker
2016-05-26 12:16 ` KOBAYASHI Shinji
2016-05-26 14:56 ` Corinna Vinschen
2016-05-26 17:21 ` KOBAYASHI Shinji
2016-05-26 17:21 ` Hans-Bernhard Bröker
2016-05-20 5:46 ` David Stacey [this message]
2016-05-20 11:36 ` Necessity for the assignment form KOBAYASHI Shinji
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=8af86ed5-e1cd-77f4-335b-d192ef3dfe6e@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--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).