Re: "Abuse" of this ML for mail-setup-test
Benjamin Kiefl <[email protected]> Fri, 11 Jul 2025 04:38:30 +0000
| Newsgroups | org.kernel.vger.linux-newbie |
|---|---|
| Message-ID | <aHCVPqH9DVYUOSSA@home> |
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. >=20 > 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 s= etup phase, but was unsure as to sending to a mailing list. But there simply see= ms to be far less "magic" to it than originally envisioned. > When using git send-email, use the --dry-run and --suppress-cc=3Dall opti= ons > to make sure you got everything right before actually sending anything. >=20 > 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 mailin= g > 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. >=20 > That way you're not making unnecessary test noises for everyone else. >=20 > Hope that helps. >=20 > -- Ryan Yep, that helps, and thanks for responding. -- Benjamin