From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <akumar@suse.de>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 5/6] doc: Update release procedure
Date: Fri, 29 Sep 2023 09:06:38 +0200 [thread overview]
Message-ID: <20230929070638.GA333901@pevik> (raw)
In-Reply-To: <12123900.MKNY5bReCh@localhost>
Hi Avinesh, Li, Cyril, all,
> Hi Petr,
> Thank you for these scripts and documentation, makes the release process very
> clear.
> I didn't try running the scripts but looks fine.
> Few minor spelling and grammatical nits below:
Avines, thanks a lot for your review and catching typos.
I shortened the output of the examples a bit and merged.
https://github.com/linux-test-project/ltp/wiki/LTP-Release-Procedure
Now waiting for CI to finish the build (just for sure) before tagging the
release and doing the rest the work.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-29 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 20:21 [LTP] [PATCH v2 0/6] Release scripts and docs Petr Vorel
2023-09-27 20:21 ` [LTP] [PATCH v2 1/6] tools: Add a script for tagging the release Petr Vorel
2023-09-27 20:21 ` [LTP] [PATCH v2 2/6] tools: Add script for creating tarballs and metadata Petr Vorel
2023-09-27 20:21 ` [LTP] [PATCH v2 3/6] doc: Rename files to names from ltp.wiki.git Petr Vorel
2023-09-27 20:21 ` [LTP] [PATCH v2 4/6] doc: Add Release procedure Petr Vorel
2023-09-27 20:21 ` [LTP] [PATCH v2 5/6] doc: Update release procedure Petr Vorel
2023-09-29 5:30 ` Avinesh Kumar
2023-09-29 7:06 ` Petr Vorel [this message]
2023-09-27 20:21 ` [LTP] [PATCH v2 6/6] Remove Makefile.release Petr Vorel
2023-09-28 7:56 ` [LTP] [PATCH v2 0/6] Release scripts and docs Li Wang
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=20230929070638.GA333901@pevik \
--to=pvorel@suse.cz \
--cc=akumar@suse.de \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.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 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.