3 ms·
>When I want to reply to someone, do I email the list or the person? How do I make sure the emails are threaded properly? Most people will (and you should, too
by ddevault 6y ago
>When I want to reply to someone, do I email the list or the person? How do I make sure the emails are threaded properly?
Most people will (and you should, too) use reply-all when participating on a mailing list, which should land the replies straight into your inbox. Just reply-all to these normally, making sure not to top post. If someone makes a mistake, and you weren't subscribed to the list, the web archives usually have a mailto: link somewhere that you can click to reply to the thread.
>The git email client seems to have support for message IDs.
You should never have to directly work with message IDs if you're using git-send-email and letting your mail client handle replies.
>Also, gmail has moved on to newer authentication mechanisms.
They should still have support for SMTP PLAIN authentication unless you use gsuite and your admin has turned it off, if I understand correctly. I have written a mail client which has support for OAUTH, however, which you might find useful:
https://aerc-mail.org https://aerc-mail.org
I don't use gmail so if you run into problems, please reach out to the appropriate mailing list - I won't know how to help.
I would also, of course, strongly recommend that you ditch gmail ASAP.
- captn3m0 6y agoThunderbird supports Gmail over OAuth.
- u801e 6y ago> You should never have to directly work with message IDs if you're using git-send-email and letting your mail client handle replies. In certain cases, if you want to include a patch in an email reply to an existing patch series (using the scissors delimiter), you would need to use git format-patch and send-email using the in-reply-to option so that the reply ends up in the correct place.
- ddevault 6y agoYeah, but I disrecommend doing this. Starting a new thread is usually better.
- u801e 6y agoBut the purpose of doing that is to provide a suggestion for a change in approach for a given patch. I don't think it would make much sense to start a new thread because you lose the association between the original approach and the modified approach. That said, I haven't seen this particular feature used in the years I've followed the git mailing list, so perhaps it's not commonly used.