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: Thu, 02 May 2013 13:28:15 -0400 [thread overview]
Message-ID: <hl8v3xmguo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <51817CF0.5070902@yandex.ru> (Dmitry Gutov's message of "Thu, 02 May 2013 00:37:04 +0400")
Dmitry Gutov wrote:
> https://github.com/mooz/js2-mode/pull/100.diff
Well, the list of reserved-words could easily have been written on a
couple of lines. It's just spread out into multiple lines due to
formatting. The real change there is just the removal of, what, ~ 10
words? Plus the doc string, total change ~ 4-5 lines IMO.
> What if the diff was adding new elements (like the reverse of this
> diff would do)? Would I be able to discount those lines then, on the
> basis that this is just copying information from the specification?
I don't really know. It's true that in the past we have been told that
information "forced by the interface" is not subject to copyright.
I'd err on the side of counting such lines though.
next prev parent reply other threads:[~2013-05-02 17:28 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=hl8v3xmguo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).