Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Difference between revisions of "Netiquette"

From eLinux.org
Jump to: navigation, search
(Created page with '== Mailing List Etiquette == Many people reading the mailing lists get irritated about top posting, and long unwrapped lines. So please configure your mailer accordingly. For p…')
 
m (Add category)
 
(4 intermediate revisions by one other user not shown)
Line 10: Line 10:
 
patch looks applied in git, you can test apply it with
 
patch looks applied in git, you can test apply it with
 
git am /path/to/the/patch.
 
git am /path/to/the/patch.
 +
 +
Any patches intended for the Linux merge window should be
 +
sent by -rc6. The merge window is for merging tested code
 +
upstream, not for integrating patches for testing. Also
 +
note that a large chunk of the patches can be sent as
 +
fixes during the -rc cycle. For fixes, please have keyword
 +
fix in the subject of the message.
  
 
Please see the following information about mailing list etiquette
 
Please see the following information about mailing list etiquette
  
* LKML FAQ Mailing List Questions: http://www.kernel.org/pub/linux/docs/lkml/#ss3
 
 
* Wiki page about interleaved posting: http://en.wikipedia.org/wiki/Top_posting#Interleaved_style
 
* Wiki page about interleaved posting: http://en.wikipedia.org/wiki/Top_posting#Interleaved_style
 +
* LKML FAQ Mailing List Questions: http://www.kernel.org/pub/linux/docs/lkml/#ss3
 +
* A page about mailing list netiquette: http://linux.sgms-centre.com/misc/netiquette.php
 +
 +
[[Category:Embedded Dictionary]]

Latest revision as of 06:15, 28 October 2011

Mailing List Etiquette

Many people reading the mailing lists get irritated about top posting, and long unwrapped lines. So please configure your mailer accordingly.

For posting patches, please post one patch per mail, and make sure the patch subject and description are suitable for applying as they are without editing. To see how your patch looks applied in git, you can test apply it with git am /path/to/the/patch.

Any patches intended for the Linux merge window should be sent by -rc6. The merge window is for merging tested code upstream, not for integrating patches for testing. Also note that a large chunk of the patches can be sent as fixes during the -rc cycle. For fixes, please have keyword fix in the subject of the message.

Please see the following information about mailing list etiquette