emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
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: Wed, 29 Jan 2020 13:47:55 +0100	[thread overview]
Message-ID: <87imkuwhs4.fsf@gnu.org> (raw)
In-Reply-To: <87sgk4o2j2.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 25 Jan 2020 00:30:57 +0100")

Hi Dan and Nicolas,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> TINYCHANGE is only about the number of non-trivial lines of code in
> your patch (15 or so).

I would not say "non-trivial lines" of code.

The change should be less *than 15 lines or so* to be accepted.

I may be wrong, but this is how I read this:
https://www.gnu.org/prep/maintain/maintain.html

I don't see any inconvenient in being strict here: this is just a
matter of signing the FSF papers for the contributors, and signing the
FSF papers is good for engaging contributors for future contributions.

Dan, if you didn't take this route yet, would you mind doing so?

Here is the form and instructions:

https://code.orgmode.org/bzg/org-mode/raw/master/request-assign-future.txt
https://orgmode.org/worg/org-contribute.html

Thanks!

-- 
 Bastien

  parent reply	other threads:[~2020-01-29 12:48 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 [this message]
2020-02-01 10:22     ` Nicolas Goaziou
2020-02-01 13:10       ` Bastien
2020-02-01 14:15         ` Nicolas Goaziou
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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87imkuwhs4.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=dan.drake@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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/org-mode.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).