linux-kernel - Re: [patch] console

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]

Date:   Tue, 22 Mar 2022 13:59:45 +0100
From:   "Alejandro Colomar (man-pages)" <alx.manpages@...il.com>
To:     nick black <dankamongmen@...il.com>
Cc:     "G. Branden Robinson" <g.branden.robinson@...il.com>,
        Michael Kerrisk <mtk.manpages@...il.com>,
        linux-kernel@...r.kernel.org, linux-man@...r.kernel.org
Subject: Re: [patch] console_codes.4: ffix

On 3/22/22 13:56, nick black wrote:
> Alejandro Colomar (man-pages) left as an exercise for the reader:
>> Patch applied.
>> However, it's weird:  I had to apply the following to your patch before
>> applying it with `git am`:
>>
>> /^diff --git/s, man4, a/man4,
>> /^diff --git/s, man4, b/man4,
>> /^--- man4/s, man4, a/man4,
>> /^+++ man4/s, man4, b/man4,
>>
>> I'm curious, how did you generate the patch?
> 
> i bounced this out from ~/Mail/sent, and have no idea how i
> originally created it, sorry =\. i'm assuming git email-send?
> 

Yeah, I guessed that you used git format-patch && git send-email, 
especially since there's a git version at the end of the patch.  The 
weird thing is that git always (AFAIK) writes (and needs) those a/ and 
b/ prefixes, so... I don't know.

If it repeats, I'll try to investigate the reason.

Thanks!

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/