From: Eryu Guan <eguan@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>, fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH 2/3] modify xfs/ quota tests to work on generic filesystems
Date: Wed, 21 Sep 2016 22:30:44 +0800 [thread overview]
Message-ID: <20160921143044.GL27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <a9112b04-17a3-dbdc-7c19-b2490875b6fd@sandeen.net>
On Wed, Sep 21, 2016 at 08:02:39AM -0500, Eric Sandeen wrote:
> >> #
> >> +# checks that xfs_quota can operate on foreign (non-xfs) filesystems
> >> +# Skips check on xfs filesystems, old xfs_quota is fine there.
> >> +# Appends "-f" to enable foreign behavior on non-xfs filesystems if available.
> >> +#
> >> +_require_xfs_quota_foreign()
> >> +{
> >> + if [ "$FSTYP" != "xfs" ]; then
> >> + $XFS_QUOTA_PROG -f -V &>/dev/null || \
> >> + _notrun "xfs_quota binary does not support foreign filesystems"
> >> + XFS_QUOTA_PROG="$XFS_QUOTA_PROG -f"
> >> + fi
> >
> > Mixing space and tab in this function.
>
> yep -
>
> As do the functions before and after it - are we going with a strict
> rule now or going for consistency with the rest of the code?
I think currently the rule is that we use tab as indentions for new
code, e.g. new functions, new tests, as long as the new code doesn't mix
with existing code. And we only go for the consistency when modifying
old code with spaces as indention.
I just searched for Dave's explanation, hope this explains better than
my words :)
- some of the code uses 4 space tabs. When adding code into
such functions, please use 4 space tabs. New code should
use 8 space tabs, but only if it's not surrounded by code
that is using 4 space tabs.
Thanks,
Eryu
next prev parent reply other threads:[~2016-09-21 14:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 22:14 [PATCH 0/3] move xfs non-project quota tests to generic Eric Sandeen
2016-09-20 22:15 ` [PATCH 1/3] xfs/260: fix output to match actions Eric Sandeen
2016-09-22 14:07 ` Bill O'Donnell
2016-09-20 22:21 ` [PATCH 2/3] modify xfs/ quota tests to work on generic filesystems Eric Sandeen
2016-09-21 9:37 ` Eryu Guan
2016-09-21 13:02 ` Eric Sandeen
2016-09-21 14:30 ` Eryu Guan [this message]
2016-09-21 14:52 ` Eric Sandeen
2016-09-22 14:09 ` Bill O'Donnell
2016-09-22 18:54 ` [PATCH 2/3 V2] " Eric Sandeen
2016-09-22 18:57 ` Bill O'Donnell
2016-09-20 22:24 ` [PATCH 3/3] move now-generic quota tests to generic Eric Sandeen
2016-09-20 23:40 ` Dave Chinner
2016-09-21 1:41 ` Eric Sandeen
2016-09-21 6:44 ` Eryu Guan
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=20160921143044.GL27776@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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