Linux Test Project
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
	Richard Palethorpe <rpalethorpe@suse.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 1/1] github: Add issue template
Date: Wed, 24 Aug 2022 16:45:13 +0200	[thread overview]
Message-ID: <YwY5eWJesAkKNQ2M@yuki> (raw)
In-Reply-To: <20220824123240.20092-1-pvorel@suse.cz>

Hi!
> this effort is driven by reports like [1]
> You can see the result on my special fork [2].
> 
> I considered to mention ML, but in the end I didn't.
> 
> Kind regards,
> Petr
> 
> [1] https://github.com/linux-test-project/ltp/issues/created_by/anilbp
> [2] https://github.com/pevik/_ltp_test_issue/issues/new
> 
>  .github/issue_template.md | 5 +++++
>  1 file changed, 5 insertions(+)
>  create mode 100644 .github/issue_template.md
> 
> diff --git a/.github/issue_template.md b/.github/issue_template.md
> new file mode 100644
> index 000000000..caf8907da
> --- /dev/null
> +++ b/.github/issue_template.md
> @@ -0,0 +1,5 @@
> +Issues are *not* support forum.
> +
> +Bugs in the tests should be reported to your Linux distribution.
> +
> +Issues are *only* for reporting bugs in tests.

I guess if we are adding this we could also include actual instruction
for a real bugreports that they should idealy include LTP version,
distribution the bug was found on, full log if applicable, etc.

-- 
Cyril Hrubis
chrubis@suse.cz

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

      parent reply	other threads:[~2022-08-24 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 12:32 [LTP] [RFC PATCH 1/1] github: Add issue template Petr Vorel
2022-08-24 13:34 ` Jan Stancek
2022-08-24 13:44   ` Petr Vorel
2022-08-24 14:45 ` Cyril Hrubis [this message]

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=YwY5eWJesAkKNQ2M@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --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