Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org,
	"Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
	"Andrzej Hajda" <andrzej.hajda@intel.com>
Subject: Re: [PATCH i-g-t v2 1/2] CONTRIBUTING: Add subscription and patchwork info
Date: Mon, 31 Mar 2025 09:54:02 -0700	[thread overview]
Message-ID: <87plhx3zv9.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250331133424.35873-2-kamil.konieczny@linux.intel.com>

On Mon, 31 Mar 2025 06:34:23 -0700, Kamil Konieczny wrote:
>
> Add guide and link to subscription into mailing list and link
> for patchwork.
>
> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Acked-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
> ---
>  CONTRIBUTING.md | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
> index 81057a2ad..8370451d6 100644
> --- a/CONTRIBUTING.md
> +++ b/CONTRIBUTING.md
> @@ -63,6 +63,13 @@ Sending Patches
>
>    on its first invocation.
>
> +- If you plan to contribute regularly, please subscribe to igt-dev mailinglist:
> +  https://lists.freedesktop.org/mailman/listinfo/igt-dev
> +  When you are not subscribed, please note that your contribution will take
> +  more time to reach to mailing list. You could find out if it was delivered or
> +  what is a testing status of your patches at page:
> +  https://patchwork.freedesktop.org/project/igt/series/

I've heard that patchwork is likely to be phased out in the future and
replaced with some infrastructure around lore.kernel.org (see below).

Maybe we can mention that emails, as well as test results, can also be seen
at:

https://lore.kernel.org/igt-dev/

> +
>  - Place relevant prefix in subject, for example when your change is in one
>    testfile, use its name without '.c' nor '.h' suffix, like:
>    tests/simple_test: short description
> --
> 2.49.0
>

  reply	other threads:[~2025-03-31 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 13:34 [PATCH i-g-t v2 0/2] CONTRIBUTING: Add subscription info, patchwork link and lib guide Kamil Konieczny
2025-03-31 13:34 ` [PATCH i-g-t v2 1/2] CONTRIBUTING: Add subscription and patchwork info Kamil Konieczny
2025-03-31 16:54   ` Dixit, Ashutosh [this message]
2025-04-01 13:36     ` Kamil Konieczny
2025-03-31 13:34 ` [PATCH i-g-t v2 2/2] CONTRIBUTING: Add guide about igt libraries Kamil Konieczny
2025-03-31 17:08   ` Dixit, Ashutosh
2025-04-01 14:22     ` Kamil Konieczny

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=87plhx3zv9.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=zbigniew.kempczynski@intel.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