From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3] man*/: srcfix
Date: Mon, 31 Jul 2023 17:23:27 -0500 [thread overview]
Message-ID: <20230731222327.l2fudhe2athgpddz@illithid> (raw)
In-Reply-To: <2fe7d79d-9fdb-4a99-1e4e-c7e847ec542b@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]
Hi Alex,
At 2023-07-31T22:38:45+0200, Alejandro Colomar wrote:
> Ahh, I'll tell you my usual routine for reviewing patches, which will
> probably explain why I didn't notice:
>
> I first try to find the signature. If there's anything not generated by
> git(1) right below the "---" and before the list of files, I read that
> first (of course after the Subject) --that's where I would have expected
> your comment to go--.
I am pretty confused. That's where I thought I put it. See screenshot.
> >>> v3: Resubmitted; no change. A revision to "MR.sed" handles this
> >>> case.
>
> Okay; your prerogative. Free Britney! :-}
Always happy to solve with sed what could be done interactively. :D
Regards,
Branden
[-- Attachment #1.2: the-v3-situation.png --]
[-- Type: image/png, Size: 45095 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-31 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 17:48 [PATCH v3] man*/: srcfix G. Branden Robinson
2023-07-31 19:56 ` Alejandro Colomar
2023-07-31 20:19 ` G. Branden Robinson
2023-07-31 20:38 ` Alejandro Colomar
2023-07-31 22:23 ` G. Branden Robinson [this message]
2023-07-31 22:55 ` Alejandro Colomar
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=20230731222327.l2fudhe2athgpddz@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.