public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi via igt-dev <igt-dev@lists.freedesktop.org>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [igt-dev] [PATCH i-g-t] doc: End transition period.
Date: Fri, 15 Feb 2019 10:57:24 -0800	[thread overview]
Message-ID: <20190215185724.11787-1-rodrigo.vivi@intel.com> (raw)
In-Reply-To: <20190215174540.18582-1-rodrigo.vivi@intel.com>

igt-dev is pretty established after a 1-year transition.

Let's end the transition and avoid confusion.

v2: Keep subjectprefix with i-g-t (Easwar)
v3: Also remove "Intel" from the line above. (Easwar)

Cc: Easwar Hariharan <easwar.hariharan@intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
 CONTRIBUTING.md | 19 +++++++------------
 1 file changed, 7 insertions(+), 12 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 27c8e796..d3a3d099 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,5 +1,5 @@
 Patches to igt-gpu-tools are very much welcome, we really want this to be the
-universal set of low-level tools and testcases for the Intel kernel gfx driver
+universal set of low-level tools and testcases for kernel graphics drivers
 on Linux and similar platforms. So please bring on porting patches, bugfixes,
 improvements for documentation and new tools and testcases.
 
@@ -10,19 +10,14 @@ A short list of contribution guidelines:
 
       Development mailing list for IGT GPU Tools <igt-dev@lists.freedesktop.org>
 
-  For a transition period patches are accepted on both the igt-dev mailing list
-  and the former intel-gfx mailing list (with the appropriate patch
-  subjectprefix, see below).
+  For patches affecting the driver directly please "cc" the appropriate driver
+  mailing list and make sure you are using:
 
-  During the transition period, feel free to send patches to both lists if you
-  have a need to do so, as they will get deduplicated so they only appear and
-  are tested in one Patchwork instance.
+      --subject-prefix="PATCH i-g-t"
 
-      Intel GFX discussion <intel-gfx@lists.freedesktop.org>
-
-  Please use --subject-prefix="PATCH i-g-t" so IGT patches are easily
-  identified in the massive amount mails on intel-gfx. To ensure this is always
-  done, meson.sh (and autogen.sh) will run:
+  so IGT patches are easily identified in the massive amount mails on driver's
+  mailing list. To ensure this is always done, meson.sh (and autogen.sh) will
+  run:
 
       git config format.subjectprefix "PATCH i-g-t"
 
-- 
2.20.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-02-15 18:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 22:18 [igt-dev] [PATCH i-g-t] doc: End transition period Rodrigo Vivi
2019-02-05 22:52 ` Antonio Argenziano
2019-02-11 19:18   ` Rodrigo Vivi
2019-02-15 10:44     ` Petri Latvala via igt-dev
2019-02-15 17:45       ` Rodrigo Vivi via igt-dev
2019-02-15 18:57         ` Rodrigo Vivi via igt-dev [this message]
2019-02-15 19:02           ` Hariharan, Easwar via igt-dev
2019-02-19 17:53             ` Rodrigo Vivi
2019-02-05 22:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-02-06  4:15 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-15 18:15 ` [igt-dev] ✓ Fi.CI.BAT: success for doc: End transition period. (rev2) Patchwork
2019-02-15 19:35 ` [igt-dev] ✓ Fi.CI.BAT: success for doc: End transition period. (rev3) Patchwork
2019-02-15 21:27 ` [igt-dev] ✗ Fi.CI.IGT: failure for doc: End transition period. (rev2) Patchwork
2019-02-16  0:07 ` [igt-dev] ✓ Fi.CI.IGT: success for doc: End transition period. (rev3) Patchwork

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=20190215185724.11787-1-rodrigo.vivi@intel.com \
    --to=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    --cc=rodrigo.vivi@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