From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
Richard Palethorpe <rpalethorpe@suse.com>
Subject: Re: [LTP] [PATCH 5/5] doc: Update release procedure
Date: Wed, 20 Sep 2023 17:39:27 +0200 [thread overview]
Message-ID: <20230920153927.GC375961@pevik> (raw)
In-Reply-To: <20230920095318.340582-6-pvorel@suse.cz>
Few formatting fixes would be needed, e.g.:
-1. Release eve work
+1 Release eve work
-------------------
-a. Collecting the (must have) patch list for new release
-b. Reviewing and merging the patch list of (a.)
-c. Widely testing, explicitly post results
-d. Tiny fix according to release testing
-e. Writing release note
+[start=a]
+.. Collecting the (must have) patch list for new release
+.. Reviewing and merging the patch list of (a.)
+.. Widely testing, explicitly post results
+.. Tiny fix according to release testing
+.. Writing release notes
But the text is what matters, thus not sending fixes before getting feedback.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-20 15:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:53 [LTP] [PATCH 0/5] Release scripts and docs Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 1/5] tools: Add a script for tagging the release Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 2/5] tools: Add script for creating tarballs and metadata Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 3/5] doc: Rename files to names from ltp.wiki.git Petr Vorel
2023-09-26 11:47 ` Cyril Hrubis
2023-09-20 9:53 ` [LTP] [PATCH 4/5] doc: Add Release procedure Petr Vorel
2023-09-26 11:46 ` Cyril Hrubis
2023-09-26 13:39 ` Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 5/5] doc: Update release procedure Petr Vorel
2023-09-20 15:29 ` Petr Vorel
2023-09-20 15:39 ` Petr Vorel [this message]
2023-09-24 0:35 ` Li Wang
2023-09-24 21:14 ` Petr Vorel
2023-09-25 2:31 ` Li Wang
2023-09-25 12:50 ` Petr Vorel
2023-09-27 6:44 ` Petr Vorel
2023-09-26 12:14 ` Cyril Hrubis
2023-09-26 13:54 ` Petr Vorel
2023-09-26 14:23 ` Cyril Hrubis
2023-09-26 15:29 ` Petr Vorel
2023-09-21 8:18 ` [LTP] [PATCH 0/5] Release scripts and docs Li Wang
2023-09-21 8:43 ` Jan Stancek
2023-09-22 16:13 ` Petr Vorel
2023-09-26 12:22 ` Cyril Hrubis
2023-09-26 13:46 ` Petr Vorel
2023-09-26 13:48 ` Cyril Hrubis
2023-09-26 12:16 ` Cyril Hrubis
2023-09-26 13:41 ` 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=20230920153927.GC375961@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
--cc=yangx.jy@cn.fujitsu.com \
/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