From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org, Adam Porter <adam@alphapapa.net>
Subject: Re: [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements
Date: Mon, 25 Mar 2024 09:17:22 +0100 [thread overview]
Message-ID: <87y1a6914d.fsf@bzg.fr> (raw)
In-Reply-To: <87sf0fa3kf.fsf@localhost> (Ihor Radchenko's message of "Sun, 24 Mar 2024 18:26:56 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Sounds reasonable.
OKay -- feel free to go ahead with whatever version you find best.
> It is a longer period compared to 5 business days mentioned in
> https://www.gnu.org/prep/maintain/maintain.html, but the copyright clerk
> is just a single guy taking care about all the requests...
Hence my proposal to wait at least for one month.
IMO it is not a problem if Org and other GNU packages propose distinct
ping'ing policies as long as the shorter period (one month for Org) is
not shorter than the one proposed for GNU in general (one week, IIUC.)
--
Bastien Guerry
next prev parent reply other threads:[~2024-03-25 8:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 12:35 [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements Ihor Radchenko
2024-03-24 17:55 ` Bastien Guerry
2024-03-24 18:26 ` Ihor Radchenko
2024-03-25 8:17 ` Bastien Guerry [this message]
2024-03-25 14:17 ` Adam Porter
2024-03-26 14:59 ` Ihor Radchenko
2024-03-27 3:23 ` Adam Porter
2024-03-28 12:01 ` Ihor Radchenko
2024-03-28 12:49 ` Adam Porter
2024-03-28 13:11 ` Ihor Radchenko
2024-03-29 18:17 ` Bastien Guerry
2024-03-30 11:08 ` Ihor Radchenko
2024-03-31 15:46 ` Adam Porter
2024-04-02 11:20 ` Ihor Radchenko
2024-04-02 23:01 ` Adam Porter
2024-04-03 0:39 ` Samuel Wales
2024-04-03 12:20 ` Ihor Radchenko
2024-04-03 12:18 ` Ihor Radchenko
2024-05-08 12:12 ` Ihor Radchenko
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=87y1a6914d.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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.