From cff17777faa93c6086226a425986644ff3fb92a1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 29 Sep 2015 11:26:42 -0400 Subject: response --- ...ent_4_433b7ba5e51e746f6b033ebb5c0e50a2._comment | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/coding_style/comment_4_433b7ba5e51e746f6b033ebb5c0e50a2._comment diff --git a/doc/coding_style/comment_4_433b7ba5e51e746f6b033ebb5c0e50a2._comment b/doc/coding_style/comment_4_433b7ba5e51e746f6b033ebb5c0e50a2._comment new file mode 100644 index 000000000..118a20caf --- /dev/null +++ b/doc/coding_style/comment_4_433b7ba5e51e746f6b033ebb5c0e50a2._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""man page style""" + date="2015-09-29T15:20:10Z" + content=""" +Well, I don't always word-wrap paras when re-editing them, and several +people have had their hands on the man page and may have different wrapping +settings. + +My suggestion would be, if you need to re-wrap, or generally make +whitespace changes, do it in a separate commit from other changes. +Similarly, make spelling corrections in a separate commit from any +substance changes. + +Note that you can push man page commits directly to this site via git:// +protocol, so it's not going to use my time as long as there's a reasonable +commit message. + +Use backticks around any command name or fragment of a command line. +Use quotes around program output, or other values that are not command +names or switch names. +"""]] -- cgit v1.2.3