All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: Petr Vorel <pevik@users.noreply.github.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] github: pull_request_template.md
Date: Mon, 15 Aug 2022 11:46:57 +0200	[thread overview]
Message-ID: <YvoWEVb9eZIHqrBI@yuki> (raw)
In-Reply-To: <20220808071439.741-2-pvorel@suse.cz>

Hi!
> Create pull request template to inform people that we prefer patches to
> our mailing list. We have this info in README.md, but even experienced,
> who send patches with git send-email to other projects overlook this
> info and open github pull requests.
> 
> While at it, add links to the test case tutorial, lore and patchwork.
> 
> Template does not support any formatting, therefore using plain links.
> 
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> NOTE: you can test it if you fork from my fork:
> https://github.com/pevik/ltp
> 
>  .github/pull_request_template.md | 6 ++++++
>  1 file changed, 6 insertions(+)
>  create mode 100644 .github/pull_request_template.md
> 
> diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
> new file mode 100644
> index 000000000..68c8a6499
> --- /dev/null
> +++ b/.github/pull_request_template.md
> @@ -0,0 +1,6 @@
> +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: https://lore.kernel.org/ltp/.
                        ^
			archived at:
> +We also have a patchwork instance: https://patchwork.ozlabs.org/project/ltp/list/.

So this text is filled in the pull request as a message when user
creates it, right?

I guess that this is a creative misuse but I kind of like it :-).

Reviewed-by: Cyril Hrubis <chrubis@suse.cz>

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2022-08-15  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  7:14 [LTP] [PATCH 0/2] github pull request template Petr Vorel
2022-08-08  7:14 ` [LTP] [PATCH 1/2] github: pull_request_template.md Petr Vorel
2022-08-15  9:46   ` Cyril Hrubis [this message]
2022-08-15 10:55     ` Petr Vorel
2022-08-15 17:14     ` Petr Vorel
2022-08-08  7:14 ` [LTP] [PATCH 2/2] doc/c-test-tutorial-simple.txt: Use links, README.md Petr Vorel
2022-08-15  9:54   ` Cyril Hrubis
2022-08-15 17:12     ` 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=YvoWEVb9eZIHqrBI@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pevik@users.noreply.github.com \
    --cc=pvorel@suse.cz \
    /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.