Difference between revisions of "Netiquette"

From eLinux.org
Jump to: navigation, search
Line 12: Line 12:
  
 
Any patches intended for the Linux merge window should be
 
Any patches intended for the Linux merge window should be
sent by -rc6. A large chunk of the patches can be sent as
+
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
 
fixes during the -rc cycle. For fixes, please have keyword
 
fix in the subject of the message.
 
fix in the subject of the message.

Revision as of 12:10, 12 March 2010

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