On 04/26/2012 01:02 PM, Subodh Nijsure wrote: ... >> Would you like me to take a stab at wordsmithing this? Something like: >> >> Each patch series should ideally start with a 0/X summary message >> explaining the purpose of the series, with each Y/X message posted as >> a reply to that summary. >> >> Post each new version of a patch series as its own thread. This avoids >> unmanageably long threads and burying new activity in old threads >> where it's less likely to be noticed. To reference a previous series, >> give a URL to a web archive, or provide the message ID, or the >> subject line and date of the previous posting. >> >> (The existing context doesn't even mention 0/5 summary messages, and the >> hunk about "When you submit or resubmit" is up at line 101 rather than >> down in the 580's...) > I struggled with putting those two paragraph up at line 101 or in > section that describes canonical patch format, decided on the later. Maybe the file will someday need structural cleanup so there's one obvious place to put this, but that's beyond the scope of this patch. > Never been good at word-smithing. > I have struggled with how does one submit patch reversions and Russell > King described it very well on arm-linux mailing list and I thought we > should capture this in documentation to help others that are just > getting started with the process. Do you want me to submit v2 or you > have it? Did my rephrase capture what you wanted to say? Rob -- GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code. Either it's "mere aggregation", or a license violation. Pick one. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
