From: Dave Chinner <david@fromorbit.com>
To: Pavel Reichl <preichl@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v4 2/4] xfs: Fix WS in xfs_isilocked() calls
Date: Wed, 12 Feb 2020 11:35:18 +1100 [thread overview]
Message-ID: <20200212003518.GP10776@dread.disaster.area> (raw)
In-Reply-To: <20200211221018.709125-2-preichl@redhat.com>
On Tue, Feb 11, 2020 at 11:10:16PM +0100, Pavel Reichl wrote:
> Signed-off-by: Pavel Reichl <preichl@redhat.com>
> ---
> fs/xfs/libxfs/xfs_bmap.c | 2 +-
> fs/xfs/xfs_file.c | 3 ++-
> fs/xfs/xfs_inode.c | 6 +++---
> fs/xfs/xfs_qm.c | 2 +-
> 4 files changed, 7 insertions(+), 6 deletions(-)
Hi Pavel,
I don't know what this patch does from reading the subject line,
and the commit message doesn't tell me, either. :)
IOWs, please don't use abbreviations in the subject line because not
everyone understands what the abbreviation you used means. This
makes it hard to read the git history once the patch is committed.
Similarly, subjects that say "Fix the frobnozzle" can be better
written as something like:
xfs: clean up whitespace in xfs_isilocked() calls
So that the output of 'git log --oneline fs/xfs' it's totally
obvious what the commit is doing from the summary. "Fix the
frobnozzle" is ambiguous because "fix" can mean many things, hence
to find out you need to look at the specific commit in more detail
and that slows down code and history searches....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2020-02-12 0:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 22:10 [PATCH v4 1/4] xfs: Refactor xfs_isilocked() Pavel Reichl
2020-02-11 22:10 ` [PATCH v4 2/4] xfs: Fix WS in xfs_isilocked() calls Pavel Reichl
2020-02-12 0:35 ` Dave Chinner [this message]
2020-02-11 22:10 ` [PATCH v4 3/4] xfs: Fix bug when checking diff. locks Pavel Reichl
2020-02-12 0:38 ` Dave Chinner
2020-02-11 22:10 ` [PATCH v4 4/4] xfs: Replace mrlock_t by rw_semaphore Pavel Reichl
2020-02-12 0:49 ` Dave Chinner
2020-02-11 22:27 ` [PATCH v4 1/4] xfs: Refactor xfs_isilocked() Eric Sandeen
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=20200212003518.GP10776@dread.disaster.area \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=preichl@redhat.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