[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1602252334400.22700@cbobk.fhfr.pm>
Date: Thu, 25 Feb 2016 23:39:04 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Chen Gang <chengang@...ndsoft.com.cn>
cc: Mel Gorman <mgorman@...hsingularity.net>,
akpm@...ux-foundation.org, vbabka@...e.cz, rientjes@...gle.com,
linux-kernel@...r.kernel.org, mhocko@...e.cz, hannes@...xchg.org,
vdavydov@...tuozzo.com, dan.j.williams@...el.com,
linux-mm@...ck.org, Chen Gang <gang.chen.5i5j@...il.com>
Subject: Re: [PATCH trivial] include/linux/gfp.h: Improve the coding styles
On Fri, 26 Feb 2016, Chen Gang wrote:
> > git blame identifies what commit last altered a line. If a cleanup patch
> > is encountered then the tree before that commit needs to be examined
> > which adds time. It's rare that cleanup patches on their own are useful
> > and this is one of those cases.
>
> git is a tool mainly for analyzing code, but not mainly for normal
> reading main code.
>
> So for me, the coding styles need not consider about git.
You are mistaken here. It's very helpful when debugging; usually you want
to find the commit that introduced particular change, and read its
changelog (at least). Having to cross rather pointless changes just adds
time (need to restart git-blame with commit~1 as a base) for no really
good reason.
Thanks,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists