From: Dan Drake <dan.drake@gmail.com>
To: Bastien <bzg@gnu.org>, 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: Sun, 2 Feb 2020 07:41:24 -0600 [thread overview]
Message-ID: <CAKqbAeFw2O9NYYjXi3s==dYW3yLYzek3wWaNySjHUV-vkfBTow@mail.gmail.com> (raw)
In-Reply-To: <87d0ayckzf.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
I just wanted to add that I have no real opinion one way or the other on
the TINYCHANGE bit; I was just following what I found at
https://orgmode.org/worg/org-contribute.html.
I also have no strong opinion on how copyright should be handled for this.
I'm willing to assign copyright to the FSF, make my contribution public
domain, or whatever is most convenient and easiest to get this into org.
Regards,
Dan
On Sat, Feb 1, 2020 at 10:48 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Bastien <bzg@gnu.org> writes:
>
> > Future maintainers may of course interpret the recommendations of
> > the FSF differently, but that's mine for now.
>
> Of course, sir.
>
--
Ceci n'est pas une .signature.
[-- Attachment #2: Type: text/html, Size: 1302 bytes --]
next prev parent reply other threads:[~2020-02-02 13:41 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
2020-02-01 14:34 ` Bastien
2020-02-01 16:48 ` Nicolas Goaziou
2020-02-02 13:41 ` Dan Drake [this message]
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='CAKqbAeFw2O9NYYjXi3s==dYW3yLYzek3wWaNySjHUV-vkfBTow@mail.gmail.com' \
--to=dan.drake@gmail.com \
--cc=bzg@gnu.org \
--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 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).