From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: oeg-add-note and double backslash ?
Date: Wed, 13 Dec 2023 10:34:03 +0000 [thread overview]
Message-ID: <87a5qexug4.fsf@localhost> (raw)
In-Reply-To: <LV8P223MB09208A821D6E39840DC9B551A28EA@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM>
David Masterson <dsmasterson@gmail.com> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> Patches welcome.
>
> * What is my status as far as submitting patches to documentation
> (including docstrings)?
I can see two commits of yours in Org repo. Beyond the 15LOC limit.
So, we cannot accept more TINYCHANGE patches and need FSF copyright
assignment - https://orgmode.org/worg/org-contribute.html#copyright
> * Is there a write-up on the process of "patching" I can follow?
Yes, of course. See https://orgmode.org/worg/org-contribute.html#first-patch
--
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>
next prev parent reply other threads:[~2023-12-13 10:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 22:37 oeg-add-note and double backslash ? David Masterson
2023-12-04 15:10 ` Ihor Radchenko
2023-12-04 22:03 ` David Masterson
2023-12-05 1:31 ` Samuel Wales
2023-12-05 6:36 ` David Masterson
2023-12-05 13:50 ` Ihor Radchenko
2023-12-07 7:52 ` David Masterson
2023-12-07 10:44 ` Ihor Radchenko
2023-12-09 2:27 ` David Masterson
2023-12-09 11:03 ` Ihor Radchenko
2023-12-10 0:23 ` David Masterson
2023-12-10 14:57 ` Ihor Radchenko
2023-12-10 21:00 ` David Masterson
2023-12-11 13:48 ` Ihor Radchenko
2023-12-12 18:29 ` David Masterson
2023-12-13 10:34 ` Ihor Radchenko [this message]
2023-12-14 5:53 ` David Masterson
2023-12-14 13:05 ` 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
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=87a5qexug4.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dsmasterson@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 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).