On Thu, Oct 22, 2015 at 04:31:44PM -0400, Chris Metcalf wrote: > So is your recommendation to avoid the git send-email --in-reply-to > option? If so, would you recommend including an lkml.kernel.org > link in the cover letter pointing to the previous version, or > is there something else that would make your workflow better? Mostly people don't bother with pointing to previous versions, and if they have the same 0/x subject, they're typically trivial to find anyway. But if you really feel the need for explicit references to previous versions, then yes, lkml.kernel.org/r/ links are preferred over pretty much anything else I think. > If you think this is actually the wrong thing, is it worth trying > to fix the git docs to deprecate this option? As said in the other email; git has different standards than lkml. By now we're just one of many many users of git. > Or is it more a question > of scale, and the 80-odd patches that I've posted so far just pushed > an otherwise good system into a more dysfunctional mode? If so, > perhaps some text in Documentation/SubmittingPatches would be > helpful here. Documentation/email-clients.txt maybe. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
