From: Josh Ponelat <jponelat@gmail.com>
To: test@public-inbox.org
Subject: Testing for RFC purposes
Date: Sat, 22 Mar 2025 14:41:22 +0200 [thread overview]
Message-ID: <CAFG41SbdMLdd1wNNr9DavAAhxvmPGVYQxjSFbVTzOwcTNLyYpg@mail.gmail.com> (raw)
Testing to see if public-inbox is a good candidate for internal RFC
processes, that are transparent and simple.
Regards,
J
next reply other threads:[~2025-03-22 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 12:41 Josh Ponelat [this message]
2025-03-22 12:57 ` Testing for RFC purposes Josh Ponelat
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=CAFG41SbdMLdd1wNNr9DavAAhxvmPGVYQxjSFbVTzOwcTNLyYpg@mail.gmail.com \
--to=jponelat@gmail.com \
--cc=test@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).