linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: nick black <dankamongmen@gmail.com>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-kernel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [patch] console_codes.4: ffix
Date: Tue, 22 Mar 2022 13:59:45 +0100	[thread overview]
Message-ID: <456bc9a8-cb58-c9ef-b1b3-3671ac34a2dc@gmail.com> (raw)
In-Reply-To: <YjnHmiYL50SqHCW/@schwarzgerat.orthanc>

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/

  reply	other threads:[~2022-03-22 12:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14  6:48 [patch] console_codes.4: ffix nick black
2022-01-17 17:30 ` Alejandro Colomar (man-pages)
2022-01-19 17:05   ` nick black
2022-01-25 17:35     ` nick black
     [not found] ` <CAN4uE+p-uKzHNYry2YhCMfEFBQ2jUqpDAGx=+eha01w-L4fAjg@mail.gmail.com>
2022-03-20 16:02   ` G. Branden Robinson
2022-03-20 18:15     ` Alejandro Colomar (man-pages)
2022-03-21  8:30       ` nick black
2022-03-22 12:27         ` Alejandro Colomar (man-pages)
2022-03-22 12:56           ` nick black
2022-03-22 12:59             ` Alejandro Colomar (man-pages) [this message]
2022-03-22 13:01               ` nick black
2022-03-21  8:33     ` nick black

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=456bc9a8-cb58-c9ef-b1b3-3671ac34a2dc@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=dankamongmen@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).