From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3] man*/: srcfix
Date: Mon, 31 Jul 2023 22:38:45 +0200 [thread overview]
Message-ID: <2fe7d79d-9fdb-4a99-1e4e-c7e847ec542b@kernel.org> (raw)
In-Reply-To: <20230731201934.gjskg73p2k33q52d@illithid>
[-- Attachment #1.1: Type: text/plain, Size: 1570 bytes --]
Hi Branden,
On 2023-07-31 22:19, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2023-07-31T21:56:27+0200, Alejandro Colomar wrote:
>> Is this that you'll do it in MR sed, or that you forgot to fix it? :D
>
> Yes, that's what I meant to indicate by the v3 annotation at the end of
> the mail.
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--.
Then I may have a fast look at the patch before applying it, especially
if I suspect I won't like it at a first glance. But if I trust the
sender, I'll directly apply it; reading diffs in the email is not very
pleasant, and git will color it nicely for me. And then I review the
patch as applied.
So, the only chance that I read personal messages like "This is just a
resend" or "I didn't provide the diff; apply the attachment" is putting
it there, right below the "---" that goes after your signature. That
part is mostly ignored by git(1) --unless the content can be confused
with a patch, I guess--.
>
>>> v3: Resubmitted; no change. A revision to "MR.sed" handles this
>>> case.
Okay; your prerogative. Free Britney! :-}
Cheers,
Alex
>
> Regards,
> Branden
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-31 20:38 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 [this message]
2023-07-31 22:23 ` G. Branden Robinson
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=2fe7d79d-9fdb-4a99-1e4e-c7e847ec542b@kernel.org \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox