However, don't go overboard with trimming. So, this would be sufficient:Īlso, it is okay to reformat the original email slightly when trimming. You should trim the parts of the quoted email that aren't relevant to your contribution. You don't need to quote all of an email in order to respond to one specific point. This is important because if someone gets cc-ed on a conversation and is missing the context, the attribution lines help them make sense of the conversation so far. Quoted text should also be preceeded by an attribution line. You can have multiple levels of replies indented like this. When quoting previous emails in our replies, we use > to differentiate the quoted text from our email. You place your replies to specific points directly under those points in the quoted text. Wrapping quoted prose is acceptable for improved readability as long as its meaning is not lost in the process. The exception to this is quoted text - the quoted text does not need to be line wrapped, especially if you are quoting someone's patch in your reply. That is, in the plain text email you send, every line will contain a carriage return character in the 72nd column or before. Lines should be wrapped at 72 characters or fewer. If you do send HTML email (please don't), at least configure your client to include a plain text alternative as an attachment. Also, HTML email will screw up the formatting of any code you quote in your email. You really don't need any fancy formatting that HTML allows. For instance, if you are sending to openstack-discuss and you want to talk about future development work on nova, your subject could be Nova should be renamed Avon instead!.įor the openstack-discuss list in particular, see the OpenStack Project Team Guide chapter on Open Community where its extensive use of topic tags is documented. Some higher-volume mailing lists recommend prefixing subject lines with topic tags in square brackets, to make threads easier for readers to quickly categorize and decide what they should read. This is an attempt to document the main points of that style. Across most open source projects a very specific email posting style is used.
0 Comments
Leave a Reply. |