From: Benjamin Kiefl <benjamin.kiefl@radonmail.net>
To: Ryan Matthews <ryanmatthews@fastmail.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: "Abuse" of this ML for mail-setup-test
Date: Fri, 11 Jul 2025 04:38:30 +0000 [thread overview]
Message-ID: <aHCVPqH9DVYUOSSA@home> (raw)
In-Reply-To: <dbb5531f-eb48-445e-b1b9-0d51481973d4@app.fastmail.com>
On Thu, Jul 10, 2025 at 11:13:30PM -0400, Ryan Matthews wrote:
> On Thu, Jul 10, 2025, at 16:46, Benjamin Kiefl wrote:
> > If there's any better way to do such a test (for potential future
> > use or setup fine-tuning) I'd also appreciate a recommendation.
>
> Actually, I suggest to experiment and practice with mutt (or any mail
> client) by sending emails back and forth to yourself between two email
> accounts. Use it to send mail to a friend. etc
Did this before sending to here of course, more than once, during initial setup
phase, but was unsure as to sending to a mailing list. But there simply seems to
be far less "magic" to it than originally envisioned.
> When using git send-email, use the --dry-run and --suppress-cc=all options
> to make sure you got everything right before actually sending anything.
>
> Then you can practice sending patches to yourself still without bothering
> mailing list or other authors.
Nice, thanks, mirrors the advice I've read elsewhere, but good to read
confirmation. Thanks for the suggestion.
> One day when you're ready to send a message or a patch to a public mailing
> list, you can do a similar test by first sending it here (but not CCing
> everyone else). Look at lore.kernel.org and see if it worked like you
> expected. Make sure it's formatted correctly in plain text, etc. Final
> step, send to the real list with all the real CCs and everything.
>
> That way you're not making unnecessary test noises for everyone else.
>
> Hope that helps.
>
> -- Ryan
Yep, that helps, and thanks for responding.
-- Benjamin
next prev parent reply other threads:[~2025-07-11 4:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 20:46 "Abuse" of this ML for mail-setup-test Benjamin Kiefl
2025-07-11 2:55 ` Ryan Matthews
2025-07-11 3:13 ` Ryan Matthews
2025-07-11 4:38 ` Benjamin Kiefl [this message]
2025-07-11 5:27 ` Unsubscribe Georges Kanaan
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=aHCVPqH9DVYUOSSA@home \
--to=benjamin.kiefl@radonmail.net \
--cc=linux-newbie@vger.kernel.org \
--cc=ryanmatthews@fastmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox