From: Bastien <bzg@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Daniel Kraus <daniel@kraus.my>, emacs-orgmode@gnu.org
Subject: Re: [WORG] Document in more detail about what maintainers do?
Date: Wed, 28 Sep 2022 08:56:57 +0200 [thread overview]
Message-ID: <87y1u4htqe.fsf@gnu.org> (raw)
In-Reply-To: <878rm4guxa.fsf@localhost> (Ihor Radchenko's message of "Wed, 28 Sep 2022 09:16:33 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
> I think the part about CC is missing in
> https://orgmode.org/worg/org-maintenance.html#orga0c76fb
Indeed - can you add it?
Also, I'd more comfortable if org-maintenance.org would use stable
anchors (not #orga0c76fb).
> Also, I find it important to take note about worg documentation for
> built-in babel backends. I did not even know it exist for a long time.
>
> WDYT?
+1 -- and also suggest adding tests, a part that I missed.
--
Bastien
next prev parent reply other threads:[~2022-09-28 7:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 15:28 [PATCH] ob-clojure.el: Add support for babashka and nbb backend Daniel Kraus
2021-11-14 16:25 ` Max Nikulin
2021-11-14 16:30 ` Daniel Kraus
2021-11-15 14:33 ` Max Nikulin
2021-11-15 16:05 ` Daniel Kraus
2021-11-17 16:12 ` Max Nikulin
2021-11-20 10:18 ` Daniel Kraus
2021-12-22 22:34 ` Daniel Kraus
2022-01-31 7:58 ` Daniel Kraus
2022-02-02 15:58 ` Max Nikulin
2022-06-11 7:45 ` Ihor Radchenko
2022-09-25 3:10 ` Bastien
2022-09-25 13:37 ` Christopher M. Miles
2022-09-25 13:43 ` Christopher M. Miles
[not found] ` <20969.6847757854$1664113375@news.gmane.org>
2022-09-25 13:48 ` Bastien
2022-09-26 16:02 ` Daniel Kraus
2022-09-27 2:31 ` Ihor Radchenko
2022-09-27 19:39 ` Bastien
2022-09-28 1:16 ` [WORG] Document in more detail about what maintainers do? (was: [PATCH] ob-clojure.el: Add support for babashka and nbb backend) Ihor Radchenko
2022-09-28 6:56 ` Bastien [this message]
2022-09-29 7:06 ` [WORG] Document in more detail about what maintainers do? Ihor Radchenko
2022-10-29 6:28 ` Ihor Radchenko
2022-10-29 8:06 ` Bastien Guerry
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=87y1u4htqe.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=daniel@kraus.my \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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).