RE: [PATCH v3] doc: writing down Git mailing list etiquette

Dave Huseby wrote:

+[[proper-use-of-to-and-cc]]
+== Proper Use of To and Cc

Always make sure the mailing list is included.

...

+[[proper-use-of-subject]]
+== Proper Use of the Subject

...

I think this is more importan than the point above.

+[[use-interleaved-style]]
+== Use Interleaved Style in Replies
+
+> A: Because it messes up the order in which people normally read text.
+> Q: Why is top-posting such a bad thing?
+> A: Top-posting.
+> Q: What is the most annoying thing in email?

You need to explain this is top-posting, and it's an example of what not
to do.

...

+[[do-not-use-mail-followup-to]]
+== Do Not Use Mail-Followup-To

...

This should be the last point.

+[[enable-plain-text-mode]]
+== Enable Plain Text Mode
+
+The Git mailing list software rejects email sent in text/html format. It is
+important that your email client is set to create text/plain emails to ensure
+delivery.

This is more important than other points.

IMO the order should be:

 1. Enable plain-text mode
 2. Proper use of subject
 3. Use interleaved-style
 4. Proper use of To/Cc
 5. Do not use mail-followup-to

...

+[[patches-that-receive-no-response]]
+== Patches that Receive No Response

I would put this in a separate patch.

Cheers.

-- 
Felipe Contreras