git/Documentation/CodingGuidelines, branch v2.2.1

Merge branch 'po/error-message-style'

2014-07-16T18:33:03Z

* po/error-message-style: doc: give some guidelines for error messages

doc: give some guidelines for error messages

2014-07-10T20:31:55Z

Clarify error message puntuation to reduce review workload. Signed-off-by: Philip Oakley Helped-by: Jeff King Signed-off-by: Junio C Hamano

CodingGuidelines: avoid "test -a/-o "

2014-05-20T18:19:43Z

The construct is error-prone; "test" being built-in in most modern shells, the reason to avoid "test && test " spawning one extra process by using a single "test -a " no longer exists. Signed-off-by: Junio C Hamano

CodingGuidelines: on splitting a long line

2014-05-02T21:08:16Z

Signed-off-by: Junio C Hamano

CodingGuidelines: on comparison

2014-05-02T20:44:46Z

There are arguments for writing a conditional as "a < b" rather than "b > a", or vice versa. Let's give guidance on which we prefer. See http://thread.gmane.org/gmane.comp.version-control.git/3903/focus=4126 for the original discussion. Signed-off-by: Junio C Hamano

CodingGuidelines: do not call the conditional statement "if()"

2014-05-02T20:26:07Z

The point immediately before it is about having SP after the control keyword. Spell it out as 'an "if" statement' instead. Signed-off-by: Junio C Hamano

CodingGuidelines: give an example for shell function preamble

2014-05-02T20:24:57Z

Signed-off-by: Junio C Hamano

CodingGuidelines: give an example for control statements

2014-05-02T20:24:57Z

Signed-off-by: Junio C Hamano

CodingGuidelines: give an example for redirection

2014-05-02T20:24:57Z

Signed-off-by: Junio C Hamano

CodingGuidelines: give an example for case/esac statement

2014-05-02T20:24:57Z

Signed-off-by: Junio C Hamano