All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kbingham@kernel.org>
To: linux-renesas-soc@vger.kernel.org,
	laurent.pinchart@ideasonboard.com,
	kieran.bingham@ideasonboard.com
Cc: Kieran Bingham <kieran@ksquared.org.uk>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: [RFC PATCH 1/3] kms-tests: Provide .gitignore
Date: Thu, 14 Dec 2017 00:25:07 +0000	[thread overview]
Message-ID: <e5595b1910e29c055c0345b2abf5d730bfaf2e31.1513211056.git-series.kieran@bingham.xyz> (raw)
In-Reply-To: <cover.417c1b91fc9842fb290756d5ad23bdc16970b1e1.1513211056.git-series.kieran@bingham.xyz>
In-Reply-To: <cover.417c1b91fc9842fb290756d5ad23bdc16970b1e1.1513211056.git-series.kieran@bingham.xyz>

From: Kieran Bingham <kieran@bingham.xyz>

From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>

Provide an initial .gitignore file to hide python related
files that may be created in an active workspace

Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
---
 .gitignore | 4 ++++
 1 file changed, 4 insertions(+)
 create mode 100644 .gitignore

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000000000000..8df6f4ad55ab
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,4 @@
+*.log
+*.swp
+*.pyc
+__pycache__
-- 
git-series 0.9.1

  reply	other threads:[~2017-12-14  0:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  0:25 [RFC PATCH 0/3] [RFC] Video HDMI Loop-back Test Kieran Bingham
2017-12-14  0:25 ` Kieran Bingham [this message]
2017-12-14  0:28   ` [RFC PATCH 1/3] kms-tests: Provide .gitignore Kieran Bingham
2017-12-14  0:25 ` [RFC PATCH 2/3] rcar_vin: Provide VIN configuration helpers Kieran Bingham
2017-12-14  0:25 ` [RFC PATCH 3/3] tests: Add a DU->VIN loopback test Kieran Bingham

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=e5595b1910e29c055c0345b2abf5d730bfaf2e31.1513211056.git-series.kieran@bingham.xyz \
    --to=kbingham@kernel.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=kieran@ksquared.org.uk \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.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.