From: Glenn Morris <rgm@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Any exceptions for the 15-line rule?
Date: Wed, 01 May 2013 12:00:30 -0400 [thread overview]
Message-ID: <y3wqriitb5.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 8761z31dv4.fsf@yandex.ru
Dmitry Gutov wrote:
> https://github.com/mooz/js2-mode/pull/101
> https://github.com/mooz/js2-mode/pull/100
>
> (add .diff at the end of each URL to see the plain diff)
I think it is fair to call those a tiny change; assuming there is
nothing else by the same author.
The 15 lines thing is not totally literal.
A mechanical s/foo/bar on a 100 lines is still a tiny change.
> On the face of it, both patches exceed 15 lines in total, but I hesitate
> to ask for CA over something this simple (this would also mean delaying
> the next merge from Git to elpa for however long that takes).
But let's not make copyright assignment out to be something daunting, or
to be avoided. It's pretty straightforward, very much so if the person
is in the USA. And if it causes a delay, well that's just how it is.
next prev parent reply other threads:[~2013-05-01 16:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 3:20 Any exceptions for the 15-line rule? Dmitry Gutov
2013-04-27 4:41 ` Stefan Monnier
2013-04-27 12:26 ` Dmitry Gutov
2013-04-27 13:28 ` Stefan Monnier
2013-04-27 13:45 ` Dmitry Gutov
2013-05-01 5:13 ` Dmitry Gutov
2013-05-01 16:00 ` Glenn Morris [this message]
2013-05-01 17:50 ` Dmitry Gutov
2013-05-01 18:06 ` Glenn Morris
2013-05-01 20:37 ` Dmitry Gutov
2013-05-02 17:28 ` Glenn Morris
2013-05-04 5:27 ` Dmitry Gutov
2013-05-05 5:02 ` Stefan Monnier
2013-05-05 7:31 ` Dmitry Gutov
2013-05-06 1:05 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2013-05-01 12:33 Barry OReilly
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=y3wqriitb5.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.