Thomas Ackermann <th.acker@xxxxxxxx> writes: >> * Documentation/git-credential.txt: >> TYPICAL USE OF GIT CREDENTIAL >> > This is to be debated because here all caps is used as "poor man's bold face" > and it would look odd if we write 'TYPICAL USE OF Git CREDENTIAL'? I left this as-is in my "fixup" commit, as the html and manpage backends seem to typeset the section titles differently. I however have to wonder what the result will look like if we replaced it with Typical use of Git credential Can you try and see how well it works? > Perhaps it would be best to separate this into 2 series: > [1/6]+[6/6] and [2/6]-[5/6]? I'd really hate to see these patches posted again to the list and asking for re-reviewing the whole thing. Can we go incremental while parking these original patches on 'pu', and later squash the whole thing into two commits, or something? Right now I have these on 'pu': b15ac19 Add rule for when to use 'git' and when to use 'Git' 57d4b2c Change 'git' to 'Git' whenever the whole system is referred to #4 01758e6 Change 'git' to 'Git' whenever the whole system is referred to #3 59b26cb Change 'git' to 'Git' whenever the whole system is referred to #2 e458530 Change 'git' to 'Git' whenever the whole system is referred to #1 c8fc93a Documentation: update two leftover small caps 170a796 Documentation: avoid poor-man's small caps I will locally squash the top one (your #6) into the bottom one (your #1). Perhaps people can proofread the result of "Some instances of 'git' should be 'Git' as they talk about the system" patches, and send in incremental corrections to be applied on top. -- 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