linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, Arusekk <arek_koz@o2.pl>,
	linux-man@vger.kernel.org,
	Eugene Syromyatnikov <evgsyr@gmail.com>
Subject: Re: [PATCH] keyctl.2: tfix
Date: Tue, 1 Dec 2020 22:53:32 +0100	[thread overview]
Message-ID: <ae5cc46c-490f-0779-d881-2aae85f4a959@gmail.com> (raw)
In-Reply-To: <39d20193-ff0a-0362-2b44-77f7c2da4978@gmail.com>

Hi Alex,

On 12/1/20 10:33 PM, Alejandro Colomar (man-pages) wrote:
> Hi Michael,
> 
> On 12/1/20 8:48 PM, Michael Kerrisk (man-pages) wrote:
>> Hi Alex,
>>
>> On 12/1/20 3:40 PM, Alejandro Colomar wrote:
>>> From: Arusekk <arek_koz@o2.pl>
>>>
>>> Fixes: fa76da808eff
>>>
>>> Signed-off-by: Arusekk <arek_koz@o2.pl>
>>> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
>>
>> Arusekk sent this patch twice. I applied the first version in my local tree,
>> but this version of the patch has a better commit message, so I dropped the 
>> old patch and applied this version instead.
> 
> Are you sure?
> I only see one patch from him.

I see now that the other patch was sent to me off-list...

> If you're seeing it on lore,
> you're probably seeing it repeated because it
> shows similar emails on the same thread even if unrelated
> (which I agree, causes some unnecessary confusion).
> 
> The only patch I see from Arusekk is:
> Message-Id: <20201201112245.11764-1-arek_koz@o2.pl>
> which has this same commit msg, but without the signature, which I added.
> 
> BTW, thanks for reviewing the other thread!

Sorry that I missed reviewing it earlier....

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2020-12-01 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01 14:40 [PATCH] keyctl.2: tfix Alejandro Colomar
2020-12-01 19:48 ` Michael Kerrisk (man-pages)
2020-12-01 21:33   ` Alejandro Colomar (man-pages)
2020-12-01 21:53     ` Michael Kerrisk (man-pages) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-01 11:22 Arusekk
2020-12-01 14:31 ` Alejandro Colomar (man-pages)
     [not found] <CAKqBPxZN3k_B5GqkmJgb9dmXh+BB0uK-S-bgBou_OJnG8HTxfQ@mail.gmail.com>
     [not found] ` <CAKqBPxZN3k_B5GqkmJgb9dmXh+BB0uK-S-bgBou_OJnG8HTxfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-25 13:32   ` [patch] " Michael Kerrisk (man-pages)

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=ae5cc46c-490f-0779-d881-2aae85f4a959@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=arek_koz@o2.pl \
    --cc=evgsyr@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;
as well as URLs for NNTP newsgroup(s).