diff mbox

Add "submitting patches" section to README

Message ID 1424816811-25516-1-git-send-email-swarren@wwwdotorg.org
State Not Applicable, archived
Headers show

Commit Message

Stephen Warren Feb. 24, 2015, 10:26 p.m. UTC 
From: Stephen Warren <swarren@nvidia.com>

This tells users how/where to send patches, etc.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
 README.txt | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

Comments

Stephen Warren Feb. 25, 2015, 11:03 p.m. UTC | #1 
On 02/24/2015 03:26 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> This tells users how/where to send patches, etc.

This patch should of course have been "[pinmux scripts PATCH]"; I didn't 
follow my own instructions on this patch:-(

Anyway, I've applied all the README patches that I sent out yesterday, for:

tegra-pinmux-scripts
tegra-uboot-scripts
cbootimage
cbootimage-configs
tegrarcm
tegra-flasher-scripts
tegra-flasher-manifests
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/README.txt b/README.txt
index 1c423d684f5e..0ca5a939670a 100644
--- a/README.txt
+++ b/README.txt
@@ -5,6 +5,27 @@  Many aspects of many of Tegra's pins can configure via the pinmux and GPIO
 controllers. This project exists to assist with software's handling of the
 configuration of those controllers.
 
+Submitting Changes
+==================
+
+To submit patches to this project, please use the following commands:
+
+* git format-patch --subject-prefix="pinmux scripts PATCH"
+
+  Creates a patch file from your git commit.
+
+* git send-email --to linux-tegra@vger.kernel.org *.patch
+
+  Sends the patch by email to the Tegra mailing list.
+
+Even though the primary upstream repository for this project is hosted on
+github, contributions aren't accepted via github pull requests. Github pull
+requests would bypass public code review on the project mailing list.
+
+Patches should be signed off (include a signed-off-by line) to indicate your
+acceptance of the code's license (see the license header in each file). See
+http://developercertificate.org/ for details of what signed-off-by implies.
+
 Data files
 ==========