> It is not a big deal for a small single-patch topic like this, but > it often is hard to reviewers if you do not respond to comments you > received and instead just send a new version of the patch with > "changes since..." comment. Please make it a habit to do both. Apologies, I am not quite used to work with a mailing list yet, I will make sure to respect this in the future! > - Have you considered using IPATTERN()? PATTERNS() that defaults > case sensitive match is suitable for real languages with fixed > case keywords, but the pattern you are defining for CSS does not > do anything special for any set of fixed-case built-in keywords, > and appears to be better served by IPATTERN(). I did have considered IPATTERN(), but assumed that case-sensitive was default and case-insensitive was the exception. As the CSS pattern does not deal with letters at all it seemed sensible to me to follow the example of the HTML pattern, which use PATTERNS(). > - In our codebase, we format multi-line comments in a particular > way, namely > > /* > * A multi-line comment begins with slash asterisk > * on its own line, and its closing asterisk slash > * also is on its own line. > */ I take good note of that. I took example on the fortran pattern comment, should I fix it too while I'm at it? > - Try not to write overlong lines. If your expression needs to > become long and there is no good place to fold lines, that is one > thing, but an overlong comment is unexcuable, as you can fold > lines anywhere between words. Again, I take good note of that. Thank you for your time! -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html