README: Update maintainers
PATCH 1/2 README: Update maintainers
Signed-off-by Paul Barker <[email protected]>
--- README | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
README +1 -2
@@ -40,8 +40,7 @@ Maintenance ----------- Maintainers: - Leo Sandoval <[email protected]> - Paul "bluelightning" Eggleton <[email protected]> + Paul Barker <[email protected]> Links -----
Signature · 1 line
2.25.0
PATCH 2/2 README: Update links and other references
* Refer to usage.adoc instead of a non-existant docs directory.
* Switch http links to https.
* Update the yocto mailing list address after the move to groups.io.
* Minor style fixes.
Signed-off-by Paul Barker <[email protected]>
--- README | 31 +++++++++++++++++-------------- 1 file changed, 17 insertions(+), 14 deletions(-)
README +17 -14
@@ -9,15 +9,16 @@ unittest python module. As input, it needs tree elements to work propertly: a patch in mbox format (either created with `git format-patch` or fetched from 'patchwork'), a test suite and a target repository. -The first test suite intended to be used with patchtest is called patchtest-oe [1], -targeted for patches that get into the openembedded-core mailing list [2] correponding -to [3] repository. +The first test suite intended to be used with patchtest is called patchtest-oe +[1], targeted for patches that get into the openembedded-core mailing list [2] +and corresponding repository [3]. -Patchtest can either run on a host or a guest machine, depending on which environment -the execution needs to be done. If you plan to test your own patches (a good practice before -these are sent to the mailing list), the easiest way is to install and execute on your local -host; in the other hand, if automatic testing is intended, the guest method -is strongly recommended. Both methods are fully explained in doc folder. +Patchtest can either run on a host or a guest machine, depending on which +environment the execution needs to be done. If you plan to test your own patches +(a good practice before these are sent to the mailing list), the easiest way is +to install and execute on your local host; in the other hand, if automatic +testing is intended, the guest method is strongly recommended. Both methods are +fully explained in usage.adoc. Installation and Usage ----------------------
@@ -27,14 +28,16 @@ Refer to the file 'usage.adoc' in this directory. Contributing ------------ -The yocto mailing list ([email protected]) is used for questions, comments and patch review. -It is subscriber only, so please register before posting. +The yocto mailing list ([email protected]) is used for questions, +comments and patch review. It is subscriber only, so please register before +posting. -Send pull requests to [email protected] with '[patchtest]' in the subject. +Send pull requests to [email protected] with '[patchtest]' in the +subject. When sending single patches, please use something like: - 'git send-email -M -1 [email protected] --subject-prefix=patchtest][PATCH' + git send-email -M -1 [email protected] --subject-prefix=patchtest][PATCH Maintenance -----------
@@ -44,6 +47,6 @@ Maintainers: Links ----- -[1] http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe/ +[1] https://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe/ [2] https://www.yoctoproject.org/tools-resources/community/mailing-lists -[3] http://git.openembedded.org/openembedded-core/ +[3] https://git.openembedded.org/openembedded-core/
Signature · 1 line
2.25.0