From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Bastien <bzg@gnu.org>
Cc: Dan Drake <dan.drake@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [RFC PATCH] specify a time, not number of minutes to keep, with org-resolve-clock
Date: Sat, 01 Feb 2020 15:15:10 +0100 [thread overview]
Message-ID: <87h80acs29.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87sgjuh2rf.fsf@gnu.org> (Bastien's message of "Sat, 01 Feb 2020 14:10:28 +0100")
Bastien <bzg@gnu.org> writes:
> My point is that distinguishing trivial vs. non-trivial parts of a
> change may be subject to interpretation. When in doubt, I recommend
> staying on the safe side of not accepting a change that is more than
> 15 lines of "maybe-significant" changes.
AFACT, there was no doubt involved when I said "15 lines of non-trivial
code".
> Yes, in this case there is no new idea, but this is irrelevant to the
> discussion,
I thought we had a discussion about it recently, but my memories may be
brittle.
> since ideas cannot be copyrighted anyway.
I knew I shouldn't have used this word. Fair enough. Replace it with
"process", or whatever has a copyright meaning.
> Well, I hope I clarified my point, which is to stay on safe side of
> asking contributors to sign the FSF papers when the importance of the
> change can be subject to intepretation.
If your point (I didn't get it actually) is "interpretation is hard,
let's not interpret anything and count everything as significant", well,
I think this is not a good way to look at the problem. But that's fine,
as long as it suits you.
Regards,
next prev parent reply other threads:[~2020-02-01 14:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 20:13 [RFC PATCH] specify a time, not number of minutes to keep, with org-resolve-clock Dan Drake
2020-01-24 23:30 ` Nicolas Goaziou
2020-01-29 2:11 ` Dan Drake
2020-01-29 9:49 ` Nicolas Goaziou
2020-01-29 12:47 ` Bastien
2020-02-01 10:22 ` Nicolas Goaziou
2020-02-01 13:10 ` Bastien
2020-02-01 14:15 ` Nicolas Goaziou [this message]
2020-02-01 14:34 ` Bastien
2020-02-01 16:48 ` Nicolas Goaziou
2020-02-02 13:41 ` Dan Drake
2020-02-02 13:51 ` Bastien
2020-02-03 14:41 ` Robert Pluim
2020-02-03 14:53 ` Bastien
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=87h80acs29.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bzg@gnu.org \
--cc=dan.drake@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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.