From: Alexey Dobriyan <adobriyan@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Stewart Malik <mali0037@gmail.com>,
aia21@cantab.net, linux-ntfs-dev@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FS: NTFS: fix whitespace and pointer issues in mst.c
Date: Sun, 7 Mar 2010 15:25:34 +0200 [thread overview]
Message-ID: <20100307132534.GA4036@x200> (raw)
In-Reply-To: <20100307121601.GJ30031@ZenIV.linux.org.uk>
On Sun, Mar 07, 2010 at 12:16:01PM +0000, Al Viro wrote:
> On Sun, Mar 07, 2010 at 10:20:51PM +1030, Stewart Malik wrote:
>
> [whitespace noise]
>
> Could we please stop using misleading subjects on that kind of patches?
More, could we please stop making git-blame output useless.
next prev parent reply other threads:[~2010-03-07 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 11:50 [PATCH] FS: NTFS: fix whitespace and pointer issues in mst.c Stewart Malik
2010-03-07 12:16 ` Al Viro
2010-03-07 13:25 ` Alexey Dobriyan [this message]
2010-03-07 19:48 ` Anton Altaparmakov
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=20100307132534.GA4036@x200 \
--to=adobriyan@gmail.com \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=mali0037@gmail.com \
--cc=viro@ZenIV.linux.org.uk \
/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