From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Petr Vorel" <pvorel@suse.cz>, <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 2/2] doc: Convert Shell API doc to RST
Date: Thu, 18 Dec 2025 13:00:53 +0100 [thread overview]
Message-ID: <DF1BR8ITX6TZ.1MY7W2QUT0WH5@suse.com> (raw)
In-Reply-To: <20251014145020.178840-2-pvorel@suse.cz>
Hi!
In general ok, but we need to keep 80 chars width of the lines.
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-12-18 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 14:50 [LTP] [PATCH 1/2] doc: Convert tst_kvercmp.h to RST Petr Vorel
2025-10-14 14:50 ` [LTP] [PATCH 2/2] doc: Convert Shell API doc " Petr Vorel
2025-12-18 12:00 ` Andrea Cervesato via ltp [this message]
2026-01-05 14:20 ` Petr Vorel
2025-10-15 10:55 ` [LTP] [PATCH 1/2] doc: Convert tst_kvercmp.h " Cyril Hrubis
2025-10-15 13:47 ` Petr Vorel
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=DF1BR8ITX6TZ.1MY7W2QUT0WH5@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=pvorel@suse.cz \
/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.