linux-kernel - Re: update checkpatch.pl to version 0.19

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: <1213009781.32207.615.camel@pmac.infradead.org>
Date:	Mon, 09 Jun 2008 12:09:41 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	Greg KH <greg@...ah.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org
Subject: Re: update checkpatch.pl to version 0.19

On Mon, 2008-06-09 at 09:33 +0100, Andy Whitcroft wrote:
> The issue I have is I have a comprehensive test suite which is kept in
> lock step with checkpatch itself, all in my own tree.  Now that is
> just noise for mainline.  What I want to be able to do is keep that in
> lock step with developments in my tree, but not merge it upstream.  So
> far I've not found a workable solution with git for that.

Why not make a tree which automatically tracks Linus' tree but only
includes checkpatch.pl. Then pull from that into your own tree before
you push your changes back.

-- 
dwmw2

--
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/