From 8737be6ab71f98afae75a57349fbfd506f53e193 Mon Sep 17 00:00:00 2001
From: oharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>
Date: Wed, 22 Oct 2008 13:40:57 +0000
Subject: [PATCH] how to send patch

git-svn-id: svn://svn.berlios.de/openocd/trunk@1089 b42882b7-edfa-0310-969c-e2dbd0fdcd60
---
 PATCHES | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 PATCHES

diff --git a/PATCHES b/PATCHES
new file mode 100644
index 000000000..8b88ecf70
--- /dev/null
+++ b/PATCHES
@@ -0,0 +1,28 @@
+Please mail patches to:
+
+openocd-development@lists.berlios.de
+
+The patch should be against svn trunk using an SVN
+diff. 
+
+Attach the patch to the email as a .txt file and
+also write a short change log entry that maintainers
+can copy and paste into the commit message
+
+Add yourself to the GPL copyright for non-trivial changes.
+
+To create a patch from the command line:
+ 
+svn diff >mypatch.txt
+
+http://svnbook.red-bean.com/en/1.0/re09.html
+
+NB! remember to use "svn add" on new files first!
+
+http://svnbook.red-bean.com/en/1.0/re01.html
+
+
+
+If you have a decent SVN GUI, then that should be
+able to create and apply patches as well...
+ 
\ No newline at end of file
-- 
GitLab