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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <540C9D19.5080201@infradead.org>
Date:	Sun, 07 Sep 2014 10:59:53 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Mark Brown <broonie@...nel.org>
CC:	Peter Foley <pefoley2@...oley.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
	Sam Ravnborg <sam@...nborg.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary
 built-in.o files

On 09/05/14 17:07, Randy Dunlap wrote:
> On 09/04/14 03:42, Mark Brown wrote:
>> On Wed, Sep 03, 2014 at 04:38:55PM -0700, Randy Dunlap wrote:
>>
>>> Hm, it could be a problem with the Index line.  I'll disable that option
>>> in quilt and see if that helps for the next time.
>>
>> Still seems to be happening today I'm afraid.
>>
> 
> I tested using git-am.  Yes, that fails.  These patch files are not emails
> but git-am expects emails and fails when it cannot find email headers (AFAICT).
> 
> Using git-apply instead of git-am does apply these patches.
> 

Hi Mark,

The quilt-import.log from 20140829 says:

$ git am --patch-format=mbox ../quilt/rd-docs/001-docum-use-subdiry-avoid-builtin.patch

and in the 20140905 git tree it says:

$ git am ../quilt/rd-docs/001-docum-use-subdiry-avoid-builtin.patch
Patch format detection failed.


Are you using Stephen's scripts?  Why would his tree apply patches with
--patch-format=mbox
while the later trees did not use that git-am option?

Thanks.

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