emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Evgenii Klimov <eugene.dev@lipklim.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] org.el: Remove undefined dynamic variable `org-log-states' from example
Date: Thu, 13 Jul 2023 11:29:32 +0000	[thread overview]
Message-ID: <87cz0wnj6r.fsf@localhost> (raw)
In-Reply-To: <87v8eodeyi.fsf@lipklim.org>

Evgenii Klimov <eugene.dev@lipklim.org> writes:

> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> It looks like 5 working days have passed since your email to FSF. If so,
>> please follow up once and wait another 5 working days.
>
> I've got papers from FSF, signed it and sent it back. It was 6 working
> days ago. 5 days that you mention is for the first response from them, I
> guess?

For any response.

The basic policy is

   When the contributor emails the form to the FSF, the FSF sends per an
   electronic (usually PDF) copy of the assignment. This, or __whatever
   response is required__, should happen within five business days of the
   initial request. If no reply from the FSF comes after that time,
   please send a reminder.
https://www.gnu.org/prep/maintain/maintain.html

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2023-07-13 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 23:11 [PATCH] org.el: Remove undefined dynamic variable `org-log-states' from example Evgenii Klimov
2023-07-11  2:24 ` Max Nikulin
2023-07-11  9:11   ` Ihor Radchenko
2023-07-12 13:42 ` Ihor Radchenko
2023-07-12 20:53   ` Evgenii Klimov
2023-07-13 11:29     ` Ihor Radchenko [this message]

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=87cz0wnj6r.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=eugene.dev@lipklim.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).