git/Documentation/CodingGuidelines, branch v2.0.2

i18n: mention "TRANSLATORS:" marker in Documentation/CodingGuidelines

2014-04-18T17:48:49Z

These comments have to have "TRANSLATORS: " at the very beginning and have to deviate from the usual multi-line comment formatting convention. Signed-off-by: Junio C Hamano

Merge branch 'jl/nor-or-nand-and'

2014-04-08T19:00:28Z

Eradicate mistaken use of "nor" (that is, essentially "nor" used not in "neither A nor B" ;-)) from in-code comments, command output strings, and documentations. * jl/nor-or-nand-and: code and test: fix misuses of "nor" comments: fix misuses of "nor" contrib: fix misuses of "nor" Documentation: fix misuses of "nor"

Documentation: fix misuses of "nor"

2014-03-31T22:16:22Z

Signed-off-by: Justin Lebar Signed-off-by: Junio C Hamano

CodingGuidelines: mention C whitespace rules

2014-02-28T20:53:50Z

We are fairly consistent about these, so most are covered by "follow existing style", but it doesn't hurt to be explicit. Signed-off-by: Jeff King Signed-off-by: Junio C Hamano

Merge branch 'jj/doc-markup-hints-in-coding-guidelines' into maint

2013-12-17T19:36:10Z

* jj/doc-markup-hints-in-coding-guidelines: State correct usage of literal examples in man pages in the coding standards

Merge branch 'jj/doc-markup-hints-in-coding-guidelines'

2013-12-03T19:41:44Z

* jj/doc-markup-hints-in-coding-guidelines: State correct usage of literal examples in man pages in the coding standards

State correct usage of literal examples in man pages in the coding standards

2013-11-18T21:30:51Z

The man pages contain inconsistent usage of backticks vs. single quotes around options, commands, etc. that are in paragraphs. This commit states that backticks should always be used around literal examples. This commit states that "--" and friends should not be escaped (e.g. use `--pretty=oneline` instead of `\--pretty=oneline`). This commit also states correct usage for typesetting command usage examples with inline substitutions. Thanks-to: Ramkumar Ramachandra Thanks-to: Stuart Rackham Thanks-to: Junio C Hamano Signed-off-by: Jason St. John Signed-off-by: Junio C Hamano

CodingGuidelines: style for multi-line comments

2013-10-14T19:48:06Z

The style for multi-line comments is often mentioned and should be documented for clarity. Signed-off-by: brian m. carlson Signed-off-by: Jonathan Nieder

Provide some linguistic guidance for the documentation.

2013-08-01T20:13:52Z

This will hopefully avoid questions over which spelling and grammar should be used. Translators are of course free to create localizations for specific English dialects. Signed-off-by: Marc Branchaud Signed-off-by: Junio C Hamano

CodingGuidelines: Documentation/*.txt are the sources

2013-05-10T19:13:08Z

People not familiar with AsciiDoc may not realize they are supposed to update *.txt files and not *.html/*.1 files when preparing patches to the project. Signed-off-by: Dale Worley Signed-off-by: Junio C Hamano