"Abuse" of this ML for mail-setup-test

"Abuse" of this ML for mail-setup-test

[Benjamin Kiefl]

Hello, I hope this is not completely out of line.

As I've never used a mailing list before, nor mutt, nor can find a purpose lkml
"testing list" for such endeavors as mine, and have witnessed this list being
low-frequency thus far, I hopefully may be exused for using this list to test
out my new setup.

An answer of any length from someone appreciated (to further test mail
reception). 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.

Cheers, looking forward to contributing to Linux,

Benjamin

Re: "Abuse" of this ML for mail-setup-test

[Ryan Matthews]

On Thu, Jul 10, 2025, at 16:46, Benjamin Kiefl wrote:
> Hello, I hope this is not completely out of line.

> Cheers, looking forward to contributing to Linux

I think it's acceptable or encouraged given your purpose.

I sent a couple test patches here a few weeks ago because I arrived at the
same conclusions. Just don't overdo it?

 -- Ryan

Re: "Abuse" of this ML for mail-setup-test

[Ryan Matthews]

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

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.

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

Re: "Abuse" of this ML for mail-setup-test

[Benjamin Kiefl]

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

Unsubscribe

[Georges Kanaan]

	Unsubscribe