All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 1 Aug 2023 00:55:46 +0200	[thread overview]
Message-ID: <afd0d893-410c-fe6e-a869-01062e301e10@kernel.org> (raw)
In-Reply-To: <20230731222327.l2fudhe2athgpddz@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 1486 bytes --]

Hi Branden,

On 2023-08-01 00:23, G. Branden Robinson wrote:
> 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.

Sorry, I didn't use precise-enough language.

I first try to find the "Signed-off-by".  The "---" (3 dashes) below marks
where the commit message ends, so anything after it --and before the diff
itself-- is ignored by git(1).

It's more or less the same as putting it in the email signature at the end,
but I don't have to scroll to the very end.

See an example:
<https://lore.kernel.org/linux-man/7c0279c1-bbb8-c623-14d2-bb4d25966d28@kernel.org/T/#mce831a3201a832ba3dc8517b934a42a5a5976e98>

Cheers,
Alex


> 
>>>>> 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

Troo.  :D

> 
> Regards,
> Branden

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-07-31 22:55 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
2023-07-31 22:55         ` Alejandro Colomar [this message]

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=afd0d893-410c-fe6e-a869-01062e301e10@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 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.