public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 0/3] Minor programming doc improvements
Date: Fri, 23 Feb 2024 14:35:05 +0100	[thread overview]
Message-ID: <20240223133505.GA1461644@pevik> (raw)
In-Reply-To: <be71af00-0f9d-4043-b6f6-f2205907ae8d@suse.com>

Hi Andrea, Marius,

> Hi!

> The whole patch is fine for me. Please merge and keep also Marius comment.

Thanks for your review, merged!

I overlooked that because I watch more patchwork than the mailing list itself.
I really need to look more into mailing list.

Could you, please, also reply to all when comment on mailing lists?
Cover letters does not your RBT (only patches themselves) + some non-regular
contributors may have unsubscribed or random people who got Cced may never has
been subscribed. Also kernel developers may not subscribe at all, because all
mailing lists on lore don't require subscription for posting messages (I've met
kernel developers posting without a subscription for this reason).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2024-02-23 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 12:34 [LTP] [PATCH 0/3] Minor programming doc improvements Petr Vorel
2023-11-03 12:34 ` [LTP] [PATCH 1/3] doc/C-Test-API: Reword SAFE_CMD() Petr Vorel
2023-11-03 12:34 ` [LTP] [PATCH 2/3] include: Add SAFE_CMD() programming doc Petr Vorel
2023-11-03 12:34 ` [LTP] [PATCH 3/3] include/tst_cmd.h: Improve " Petr Vorel
2023-11-03 15:12 ` [LTP] [PATCH 0/3] Minor programming doc improvements Marius Kittler
2024-02-21 14:36 ` Andrea Cervesato via ltp
2024-02-23 13:35   ` Petr Vorel [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=20240223133505.GA1461644@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --cc=ltp@lists.linux.it \
    /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