ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Richard Palethorpe <rpalethorpe@suse.com>,
	Xiao Yang <yangx.jy@cn.fujitsu.com>
Subject: [LTP] [RFC PATCH 0/2] Wiki: files rename,add 'Release procedure'
Date: Tue, 28 Mar 2023 13:13:36 +0200	[thread overview]
Message-ID: <20230328111338.766712-1-pvorel@suse.cz> (raw)

Petr Vorel (2):
  doc: Rename files to names from ltp.wiki.git
  doc: Add Release procedure

 .github/workflows/wiki-mirror.yml             | 16 +----
 ...ild-system-guide.txt => Build-System.rest} |  0
 doc/{c-test-api.txt => C-Test-API.asciidoc}   |  0
 ...mple.txt => C-Test-Case-Tutorial.asciidoc} |  0
 ...-c-api.txt => C-Test-Network-API.asciidoc} |  0
 ...kvm-test-api.txt => KVM-Test-API.asciidoc} |  0
 ...P-Library-API-Writing-Guidelines.asciidoc} |  0
 doc/LTP-Release-Procedure.asciidoc            | 67 +++++++++++++++++++
 ...aintainer-Patch-Review-Checklist.asciidoc} |  0
 ...l-test-api.txt => Shell-Test-API.asciidoc} |  0
 ...kernel,-libc,-toolchain-versions.asciidoc} |  0
 ...s.txt => Test-Writing-Guidelines.asciidoc} |  0
 ...ser-guide.txt => User-Guidelines.asciidoc} |  0
 13 files changed, 70 insertions(+), 13 deletions(-)
 rename doc/{build-system-guide.txt => Build-System.rest} (100%)
 rename doc/{c-test-api.txt => C-Test-API.asciidoc} (100%)
 rename doc/{c-test-tutorial-simple.txt => C-Test-Case-Tutorial.asciidoc} (100%)
 rename doc/{network-c-api.txt => C-Test-Network-API.asciidoc} (100%)
 rename doc/{kvm-test-api.txt => KVM-Test-API.asciidoc} (100%)
 rename doc/{library-api-writing-guidelines.txt => LTP-Library-API-Writing-Guidelines.asciidoc} (100%)
 create mode 100644 doc/LTP-Release-Procedure.asciidoc
 rename doc/{maintainer-patch-review-checklist.txt => Maintainer-Patch-Review-Checklist.asciidoc} (100%)
 rename doc/{shell-test-api.txt => Shell-Test-API.asciidoc} (100%)
 rename doc/{supported-kernel-libc-versions.txt => Supported-kernel,-libc,-toolchain-versions.asciidoc} (100%)
 rename doc/{test-writing-guidelines.txt => Test-Writing-Guidelines.asciidoc} (100%)
 rename doc/{user-guide.txt => User-Guidelines.asciidoc} (100%)

-- 
2.40.0


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

             reply	other threads:[~2023-03-28 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 11:13 Petr Vorel [this message]
2023-03-28 11:13 ` [LTP] [RFC PATCH 1/2] doc: Rename files to names from ltp.wiki.git Petr Vorel
2023-03-28 11:13 ` [LTP] [RFC PATCH 2/2] doc: Add Release procedure Petr Vorel
2023-03-28 12:42   ` Li Wang
2023-03-28 13:04     ` 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=20230328111338.766712-1-pvorel@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).