git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
	Christian Couder <christian.couder@gmail.com>,
	Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCHv2 1/7] CodingGuidelines: mention whitespace preferences for shell scripts
Date: Fri, 3 Dec 2010 23:02:03 +0100	[thread overview]
Message-ID: <AANLkTi=PmGR23AMog4UWQVNKPWrDUM_kYWV_Bn1vvSwE@mail.gmail.com> (raw)
In-Reply-To: <7vsjyemt1f.fsf@alter.siamese.dyndns.org>

On Fri, Dec 3, 2010 at 10:43 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:
>
>> Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
>> ---
>>  Documentation/CodingGuidelines |    4 ++++
>>  1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
>> index 5aa2d34..a9191d0 100644
>> --- a/Documentation/CodingGuidelines
>> +++ b/Documentation/CodingGuidelines
>> @@ -31,6 +31,10 @@ But if you must have a list of rules, here they are.
>>
>>  For shell scripts specifically (not exhaustive):
>>
>> + - We use tabs for indentation.
>> +
>> + - Case arms are not indented with respect to the case and esac lines.
>
> Thanks.
> I am tempted to rephrase the latter as:
>
>    Case arms are indented at the same depth as case and esac lines.
>
> It makes it less hard to read and understand without negation.

Good idea. I'll rephrase in that sense and add a couple more entries
about the | spacing and long case arm splitting, for the next rehash
of the series.

-- 
Giuseppe "Oblomov" Bilotta

  reply	other threads:[~2010-12-03 22:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 16:47 [PATCHv2 0/7] web--browse cleanup and extensions Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 1/7] CodingGuidelines: mention whitespace preferences for shell scripts Giuseppe Bilotta
2010-12-03 21:43   ` Junio C Hamano
2010-12-03 22:02     ` Giuseppe Bilotta [this message]
2010-12-03 22:28       ` Junio C Hamano
2010-12-03 22:46         ` Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 2/7] web--browse: coding style Giuseppe Bilotta
2010-12-07 23:38   ` Junio C Hamano
2010-12-03 16:47 ` [PATCHv2 3/7] web--browse: split valid_tool list Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 4/7] web--browse: support opera, seamonkey and elinks Giuseppe Bilotta
2010-12-03 22:01   ` Junio C Hamano
2010-12-03 22:22     ` Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 5/7] web--browse: better support for chromium Giuseppe Bilotta
2010-12-03 21:57   ` Junio C Hamano
2010-12-03 22:25     ` Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 6/7] web--browse: use (x-)www-browser if available Giuseppe Bilotta
2010-12-03 17:40   ` Christian Couder
2010-12-03 17:57     ` Giuseppe Bilotta
2010-12-03 22:15   ` Junio C Hamano
2010-12-03 22:45     ` Giuseppe Bilotta
2010-12-04  0:42       ` Jonathan Nieder
2010-12-04  7:49         ` Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 7/7] web--browse: look at the BROWSER env var Giuseppe Bilotta
2010-12-03 17:08   ` Jonathan Nieder
2010-12-03 17:16     ` Jonathan Nieder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=PmGR23AMog4UWQVNKPWrDUM_kYWV_Bn1vvSwE@mail.gmail.com' \
    --to=giuseppe.bilotta@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).