On Wed, Sep 19, 2018 at 5:36 AM Eric Sunshine wrote:
>
> On Tue, Sep 18, 2018 at 10:11 PM Matthew DeVore wrote:
> > Yes, it's probably better to add a point about that. Here is the new
> > documentation after applying your suggestions:
> >
> > - If a piped sequence which spans multiple lines, pu
Matthew DeVore writes:
> Yes, it's probably better to add a point about that. Here is the new
> documentation after applying your suggestions:
>
> - If a piped sequence which spans multiple lines, put each statement
>on a separate line and put pipes on the end of each line, rather
>than
On Tue, Sep 18, 2018 at 10:11 PM Matthew DeVore wrote:
> Yes, it's probably better to add a point about that. Here is the new
> documentation after applying your suggestions:
>
> - If a piped sequence which spans multiple lines, put each statement
s/which//
>on a separate line and put pipes
On Mon, Sep 17, 2018 at 5:16 PM Eric Sunshine wrote:
>
> On Mon, Sep 17, 2018 at 6:24 PM Matthew DeVore wrote:
> > diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
> > @@ -163,6 +163,35 @@ For shell scripts specifically (not exhaustive):
> > + - In a piped sequence whi
On Mon, Sep 17, 2018 at 6:24 PM Matthew DeVore wrote:
> diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
> @@ -163,6 +163,35 @@ For shell scripts specifically (not exhaustive):
> + - In a piped sequence which spans multiple lines, put each statement
> + on a separate
Add two guidelines:
- pipe characters should appear at the end of lines, and not cause
indentation
- pipes should be avoided when they swallow exit codes that can
potentially fail
---
Documentation/CodingGuidelines | 29 +
1 file changed, 29 insertions(+)
diff
6 matches
Mail list logo