From: Randy Dunlap <rdunlap@infradead.org>
To: SeongJae Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] Docs/process/email-clients: Document HacKerMaiL
Date: Tue, 25 Jun 2024 15:16:23 -0700 [thread overview]
Message-ID: <61deba2b-3791-4ceb-a02c-de3bbca2426b@infradead.org> (raw)
In-Reply-To: <20240624185312.94537-8-sj@kernel.org>
On 6/24/24 11:53 AM, SeongJae Park wrote:
> HacKerMaiL (hkml) [1] is a simple tool for mailing lists-based
> development workflows such as that for most Linux kernel subsystems. It
> is actively being maintained by DAMON maintainer, and recommended for
> DAMON community[2]. Add a simple introduction of the tool on the
> email-clients document, too.
>
> [1] https://github.com/sjp38/hackermail
> [2] https://lore.kernel.org/20240621170353.BFB83C2BBFC@smtp.kernel.org
>
> Signed-off-by: SeongJae Park <sj@kernel.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/process/email-clients.rst | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/process/email-clients.rst b/Documentation/process/email-clients.rst
> index fc2c46f3f82d..dd22c46d1d02 100644
> --- a/Documentation/process/email-clients.rst
> +++ b/Documentation/process/email-clients.rst
> @@ -350,3 +350,12 @@ although tab2space problem can be solved with external editor.
>
> Another problem is that Gmail will base64-encode any message that has a
> non-ASCII character. That includes things like European names.
> +
> +HacKerMaiL (TUI)
> +****************
> +
> +HacKerMaiL (hkml) is a public-inbox based simple mails management tool that
> +doesn't require subscription of mailing lists. It is developed and maintained
> +by the DAMON maintainer and aims to support simple development workflows for
> +DAMON and general kernel subsystems. Refer to the README
> +(https://github.com/sjp38/hackermail/blob/master/README.md) for details.
--
~Randy
next prev parent reply other threads:[~2024-06-25 22:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 18:53 [PATCH 0/7] minor document fixups SeongJae Park
2024-06-24 18:53 ` [PATCH 1/7] Docs/process/index: Remove unaligned-memory-access from 'Other material' SeongJae Park
2024-06-24 18:53 ` [PATCH 2/7] Docs/process/index: Remove riscv/patch-acceptance from 'Other material' section SeongJae Park
2024-06-24 18:53 ` [PATCH 3/7] Docs: Move magic-number from process to staging SeongJae Park
2024-06-25 7:50 ` Federico Vaga
2024-06-26 22:34 ` Jonathan Corbet
2024-06-24 18:53 ` [PATCH 4/7] Docs: Move clang-format from process/ to dev-tools/ SeongJae Park
2024-06-24 19:26 ` Miguel Ojeda
2024-06-25 7:51 ` Federico Vaga
2024-06-24 18:53 ` [PATCH 5/7] Docs/process/index: Remove unsorted docs section SeongJae Park
2024-06-24 18:53 ` [PATCH 6/7] Docs/maintainer/maintainer-entry-profile: add DAMON maintainer profile SeongJae Park
2024-06-24 18:53 ` [PATCH 7/7] Docs/process/email-clients: Document HacKerMaiL SeongJae Park
2024-06-25 22:16 ` Randy Dunlap [this message]
2024-06-26 22:35 ` Jonathan Corbet
2024-06-26 22:48 ` SeongJae Park
2024-06-26 22:50 ` [PATCH 0/7] minor document fixups Jonathan Corbet
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=61deba2b-3791-4ceb-a02c-de3bbca2426b@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj@kernel.org \
--cc=workflows@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox