From: Richard Palethorpe <rpalethorpe@suse.de>
To: Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] github: Improve pull request template
Date: Tue, 10 Jan 2023 09:56:42 +0000 [thread overview]
Message-ID: <874jsyiufl.fsf@suse.de> (raw)
In-Reply-To: <2226132.28uSQYClPH@localhost>
Hello,
Please merge.
Acked-by: Richard Palethorpe <rpalethorpe@suse.com>
Avinesh Kumar <akumar@suse.de> writes:
> Hi,
>
> Reviewed-by: Avinesh Kumar <akumar@suse.de>
>
> On Wednesday, January 4, 2023 3:37:30 PM IST Petr Vorel wrote:
>> * Signed-off-by
>> * code style
>> * links to wiki (API, maintainer checklist, ...)
>> * wrap text in html comments (instructions will not be visible)
>>
>> Signed-off-by: Petr Vorel <pvorel@suse.cz>
>> ---
>> .github/pull_request_template.md | 20 +++++++++++++++++---
>> 1 file changed, 17 insertions(+), 3 deletions(-)
>>
>> diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
>> index 477f49c6bc..1082bcdd88 100644
>> --- a/.github/pull_request_template.md
>> +++ b/.github/pull_request_template.md
>> @@ -1,8 +1,22 @@
>> [ type description here; PLEASE REMOVE THIS LINE AND THE LINES BELOW BEFORE SUBMITTING THIS PULL REQUEST ]
>>
>> -Although we *occasionally* also accept GitHub pull requests, the *preferred* way is sending patches to our mailing list: https://lore.kernel.org/ltp/
>> -
>> +<!--
>> +* Although we *occasionally* also accept GitHub pull requests, the *preferred* way is sending patches to our mailing list: https://lore.kernel.org/ltp/
>> There is an example how to use it:
>> https://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial#7-submitting-the-test-for-review
>> (using git format-patch and git send-email).
>> -
>> LTP mailing list is archived at: https://lore.kernel.org/ltp/.
>> We also have a patchwork instance: https://patchwork.ozlabs.org/project/ltp/list/.
>> +
>> +* Commits should be signed: Signed-off-by: Your Name <me@example.org>, see
>> +https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
>> +
>> +* New code should follow Linux kernel coding style, see
>> +https://www.kernel.org/doc/html/latest/process/coding-style.html.
>> +You can run 'make check' or 'make check-foo' in the folder with modified code to check style and common errors.
>> +
>> +* For more tips check
>> +https://github.com/linux-test-project/ltp/wiki/Maintainer-Patch-Review-Checklist
>> +https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines
>> +https://github.com/linux-test-project/ltp/wiki/C-Test-API
>> +https://github.com/linux-test-project/ltp/wiki/Shell-Test-API
>> +https://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial
>> +-->
>>
>
> Regards,
> Avinesh
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-01-10 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 10:07 [LTP] [PATCH 1/1] github: Improve pull request template Petr Vorel
2023-01-09 11:05 ` Avinesh Kumar
2023-01-10 9:56 ` Richard Palethorpe [this message]
2023-01-10 10:26 ` Petr Vorel
2023-01-10 10:38 ` Avinesh Kumar
2023-01-10 10:38 ` Richard Palethorpe
2023-01-10 16:04 ` Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 8: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=874jsyiufl.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=akumar@suse.de \
--cc=ltp@lists.linux.it \
/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.