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: <1319672648.21924.26.camel@Joe-Laptop>
Date:	Wed, 26 Oct 2011 16:44:08 -0700
From:	Joe Perches <joe@...ches.com>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Wolfram Sang <w.sang@...gutronix.de>, linux-kernel@...r.kernel.org,
	Jonathan Cameron <jic23@....ac.uk>,
	Andy Whitcroft <apw@...onical.com>
Subject: Re: [PATCH] checkpatch: improve error message for p1-check

On Wed, 2011-10-26 at 16:34 -0700, David Rientjes wrote:
> On Wed, 26 Oct 2011, Joe Perches wrote:
> > > So we need a combination of the two approaches then, it makes sense to 
> > > only emit the warning if the patched file exists in both prefixes.
> > I don't think so.  What about something like:
> > $ diff -urN kernel/foo~ kernel/foo > patch
> > I think we should only care about the patched file,.
> I mean it only makes sense if both prefixes exist (otherwise patch and 
> git-apply will assume it's not a -p0 patch).

I think we should not care about the prefixes at all,
only whether or not the patched file exists.


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