All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rhys Kidd <rhyskidd@gmail.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v2 4/5] doc: Update CONTRIBUTING for new igt-dev mailing list
Date: Fri, 19 Jan 2018 19:25:25 -0500	[thread overview]
Message-ID: <20180120002526.18016-4-rhyskidd@gmail.com> (raw)
In-Reply-To: <20180120002526.18016-1-rhyskidd@gmail.com>

v2: Modify comments for feedback received (Petri Latvala)

Signed-off-by: Rhys Kidd <rhyskidd@gmail.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
---
 CONTRIBUTING | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 5600caaf..0180641b 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -6,11 +6,21 @@ improvements for documentation and new tools and testcases.
 A short list of contribution guidelines:
 
 - Please submit patches formatted with git send-email/git format-patch or
-  equivalent to
+  equivalent to:
+
+    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).
+
+  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.
 
     Intel GFX discussion <intel-gfx@lists.freedesktop.org>
 
-  Please use --subject-prefix="PATCH i-g-t" so that i-g-t patches are easily
+  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:
 
@@ -36,7 +46,7 @@ A short list of contribution guidelines:
   anything related to the regular releases, issues with packaging and
   integrating platform support or any other intel-gpu-tools issues, please
   contact one of the maintainers (listed in the MAINTAINERS file) and cc the
-  intel-gfx mailing list.
+  igt-dev mailing list.
 
 - Changes to the testcases are automatically tested. Take the results into
   account before merging.
-- 
2.14.1

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

  parent reply	other threads:[~2018-01-20  0:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180117052337.22424-1-rhyskidd@gmail.com>
     [not found] ` <20180117052337.22424-4-rhyskidd@gmail.com>
2018-01-18 12:10   ` [igt-dev] [PATCH i-g-t 4/5] doc: Update CONTRIBUTING for new igt-dev mailing list Petri Latvala
2018-01-18 12:35 ` [igt-dev] [PATCH i-g-t 1/5] doc: Fix typos in CONTRIBUTING Petri Latvala
2018-01-20  0:25   ` [igt-dev] [PATCH i-g-t v2 " Rhys Kidd
2018-01-20  0:25     ` [igt-dev] [PATCH i-g-t v2 2/5] lib/igt.cocci: Fix typo Rhys Kidd
2018-01-20  0:25     ` [igt-dev] [PATCH i-g-t v2 3/5] doc: Correct sentence in README Rhys Kidd
2018-01-20  0:25     ` Rhys Kidd [this message]
2018-01-20  0:25     ` [igt-dev] [PATCH i-g-t v2 5/5] man: Update for new igt-dev mailing list Rhys Kidd
2018-01-23  4:43 [igt-dev] [PATCH i-g-t v2 1/5] doc: Fix typos in CONTRIBUTING Rhys Kidd
2018-01-23  4:43 ` [igt-dev] [PATCH i-g-t v2 4/5] doc: Update CONTRIBUTING for new igt-dev mailing list Rhys Kidd

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=20180120002526.18016-4-rhyskidd@gmail.com \
    --to=rhyskidd@gmail.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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.