From: Rhys Kidd <rhyskidd@gmail.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v2 1/5] doc: Fix typos in CONTRIBUTING
Date: Fri, 19 Jan 2018 19:25:22 -0500 [thread overview]
Message-ID: <20180120002526.18016-1-rhyskidd@gmail.com> (raw)
In-Reply-To: <20180118123522.6mi53rnzlpykosas@platvala-desk.ger.corp.intel.com>
Signed-off-by: Rhys Kidd <rhyskidd@gmail.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
---
CONTRIBUTING | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/CONTRIBUTING b/CONTRIBUTING
index aa555aa1..5600caaf 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -29,7 +29,7 @@ A short list of contribution guidelines:
- Patches need to be reviewed on the mailing list. Exceptions only apply for
testcases and tooling for drivers with just a single contributor (e.g. vc4).
In this case patches must still be submitted to the mailing list first.
- Testcase should preferrably be cross-reviewed by the same people who write and
+ Testcase should preferably be cross-reviewed by the same people who write and
review the kernel feature itself.
- When patches from new contributors (without commit access) are stuck, for
@@ -38,9 +38,7 @@ A short list of contribution guidelines:
contact one of the maintainers (listed in the MAINTAINERS file) and cc the
intel-gfx mailing list.
-- Especially changes to the testcase should get tested on relevant platforms
- before committing. For Intel employees that's best done using PRTS, see the
- relevant internal howtos. Everyone else can just run piglit with i-g-t tests
- locally.
+- Changes to the testcases are automatically tested. Take the results into
+ account before merging.
Happy hacking!
--
2.14.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-01-20 0:25 UTC|newest]
Thread overview: 9+ 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 ` Rhys Kidd [this message]
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 ` [igt-dev] [PATCH i-g-t v2 4/5] doc: Update CONTRIBUTING for new igt-dev mailing list Rhys Kidd
2018-01-20 0:25 ` [igt-dev] [PATCH i-g-t v2 5/5] man: Update " 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 9:16 ` Petri Latvala
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-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox