From: nick black <dankamongmen@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@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 08:56:58 -0400 [thread overview]
Message-ID: <YjnHmiYL50SqHCW/@schwarzgerat.orthanc> (raw)
In-Reply-To: <809c40c4-068b-8296-57d9-024e6623362d@gmail.com>
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?
--
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.
next prev parent reply other threads:[~2022-03-22 12:57 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 [this message]
2022-03-22 12:59 ` Alejandro Colomar (man-pages)
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=YjnHmiYL50SqHCW/@schwarzgerat.orthanc \
--to=dankamongmen@gmail.com \
--cc=alx.manpages@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).