From: Mel Gorman <mgorman@suse.de>
To: Zhihui Zhang <zzhsuny@gmail.com>
Cc: trivial@kernel.org, akpm@linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [PATCH] [mm] trivial fixes to long lines and typo in comment
Date: Sat, 29 Nov 2014 16:02:02 +0000 [thread overview]
Message-ID: <20141129160201.GT2725@suse.de> (raw)
In-Reply-To: <1417276019-17792-1-git-send-email-zzhsuny@gmail.com>
On Sat, Nov 29, 2014 at 10:46:59AM -0500, Zhihui Zhang wrote:
> Well, the subject line says it all.
>
Why bother?
It adds almost nothing (one meaningful change) and git blame would no
longer points to the commit that actually modified that introduced or last
updated those comments.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2014-11-29 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 15:46 [PATCH] [mm] trivial fixes to long lines and typo in comment Zhihui Zhang
2014-11-29 16:02 ` Mel Gorman [this message]
2014-11-29 21:08 ` Jiri Kosina
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=20141129160201.GT2725@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=zzhsuny@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