lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEUsAPb7dHfmEJikk8Xfx1YKrZd3p1vimo_rh3SE4ckqzZShYA@mail.gmail.com>
Date:	Sat, 10 Jan 2015 14:08:00 -0600
From:	Chris Rorvick <chris@...vick.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Andy Whitcroft <apw@...onical.com>,
	Prarit Bhargava <prarit@...hat.com>,
	Daniel Baluta <daniel.baluta@...el.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] checkpatch: Update git commit message

On Fri, Jan 9, 2015 at 3:58 PM, Joe Perches <joe@...ches.com> wrote:
> The git commit message can be confusing,
>
> Try to clarify the message a bit to reduce
> the confusion when emitted.

I just ignored a few GIT_COMMIT_ID errors last night because I was
confused by the message.  My mistake was forgetting to quote the commit
summary.  Running checkpatch with this makes the problem clear.

Tested-by: Chris Rorvick <chris@...vick.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ