Coexist with quilt: rename PATCHES --> PATCHES.txt

The issues is on Win32, which ignores case in filesystem
and thus doesn't tolerate the quilt "patches" directory.

Rename, and add "patches" to .gitignore so that developers
can choose to use quilt for local patch management.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>

diff --git a/.gitignore b/.gitignore
index 5ec831ed84b91a5b9da58fdd45da68c1af5e3d03..e37ee5a14c1cd2f1f98c63b6658bc345b2ce13b4 100644 (file)
--- a/.gitignore
+++ b/.gitignore
@@ -66,6 +66,9 @@ stamp-vti
 INSTALL
 NOTES
 
+# coexist with quilt
+patches
+
 # Eclipse stuff
 .project
 .cproject

diff --git a/BUGS b/BUGS
index 961b33940a4b5f6f31a2b3c2f8d2e03d436c7bc2..36a7da376f05af4743838bdad2fe44a5fba7fd56 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -26,8 +26,8 @@ that may be important.
     http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
 
 If possible, please develop and attach a patch that helps to expose or
-solve the reported problem.  See the PATCHES file for more information
-for that process.
+solve the reported problem.  See the PATCHES.txt file for information
+about that process.
 
 Attach all files directly to your posting.  The mailing list knows to
 transform attachments to links, but attachments must be less than 300KB

diff --git a/Doxyfile.in b/Doxyfile.in
index 49630f2ffb8d8eb397524dfc3cba273800959f95..519bb2f82cb46f3e5417fe9f5a2cc41554919971 100644 (file)
--- a/Doxyfile.in
+++ b/Doxyfile.in
@@ -567,7 +567,7 @@ WARN_LOGFILE           =
 INPUT                  = @srcdir@/doc/manual \
                          @srcdir@/TODO \
                          @srcdir@/BUGS \
-                         @srcdir@/PATCHES \
+                         @srcdir@/PATCHES.txt \
                          @srcdir@/src \
                          @srcdir@/config.h
 

diff --git a/NEWS b/NEWS
index ba7e0e60dca24cadfe8be205e7a81c681f3c6b25..b1696065127439b96471f0f170b3a6e8a02bb098 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -8,6 +8,7 @@ JTAG Layer:
        Support USB-JTAG, Altera USB-Blaster and compatibles.
 
 Boundary Scan:
+
 Target Layer:
        General
                - new "reset-assert" event, for systems without SRST
@@ -36,6 +37,8 @@ Target Layer:
        ETM, ETB
                - "trigger_percent" command moved ETM --> ETB
                - "etm trigger_debug" command added
+       MIPS
+               - use fastdata writes
        Freescale DSP563xx cores (partial support)
 
 Flash Layer:
@@ -81,4 +84,4 @@ For older NEWS, see the NEWS files associated with each release
 
 For more information about contributing test reports, bug fixes, or new
 features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES files in the source archive).
+the BUGS and PATCHES.txt files in the source archive).

diff --git a/PATCHES b/PATCHES
deleted file mode 100644 (file)
index 856b094..0000000
--- a/PATCHES
+++ /dev/null
@@ -1,47 +0,0 @@
-// This file is part of the Doxygen Developer Manual
-/** @page patchguide Patch Guidelines
-
-Please mail patches to: @par
-       openocd-development@lists.berlios.de
-
-Note that you can't send patches to that list unless
-you're a member, despite what the list info page says.
-
-@section Patch Guidelines in a Nutshell
-
-Your patches should be against git mainline.  Submit output
-of "git diff"; equivalently, quilt patches are OK.
-
-It should be a "good patch": focus it on a single
-issue, and make it be easily reviewable. Don't make
-it so large that it's hard to review; split large
-patches into smaller ones. (That can also help
-track down bugs later on.) All patches should
-be "clean", which includes preserving the existing
-coding style and updating documentation as needed.j
-
-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
-
-Say if it's a bugfix (describe the bug) or a new
-feature. Don't expect patches to merge immediately
-for the next release. Be ready to rework patches
-in response to feedback.
-
-Add yourself to the GPL copyright for non-trivial changes.
-
-To create a patch from the command line:
-@code
-       git diff >mypatch.txt
-@endcode
-
-@section More Information on Patching
-
-The @ref primerpatches provides a more complete guide to creating,
-managing, and contributing patches to the OpenOCD project.
-
- */
-/** @file
-This file contains the @ref patchguide page.
-*/

diff --git a/PATCHES.txt b/PATCHES.txt
new file mode 100644 (file)
index 0000000..856b094
--- /dev/null
+++ b/PATCHES.txt
@@ -0,0 +1,47 @@
+// This file is part of the Doxygen Developer Manual
+/** @page patchguide Patch Guidelines
+
+Please mail patches to: @par
+       openocd-development@lists.berlios.de
+
+Note that you can't send patches to that list unless
+you're a member, despite what the list info page says.
+
+@section Patch Guidelines in a Nutshell
+
+Your patches should be against git mainline.  Submit output
+of "git diff"; equivalently, quilt patches are OK.
+
+It should be a "good patch": focus it on a single
+issue, and make it be easily reviewable. Don't make
+it so large that it's hard to review; split large
+patches into smaller ones. (That can also help
+track down bugs later on.) All patches should
+be "clean", which includes preserving the existing
+coding style and updating documentation as needed.j
+
+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
+
+Say if it's a bugfix (describe the bug) or a new
+feature. Don't expect patches to merge immediately
+for the next release. Be ready to rework patches
+in response to feedback.
+
+Add yourself to the GPL copyright for non-trivial changes.
+
+To create a patch from the command line:
+@code
+       git diff >mypatch.txt
+@endcode
+
+@section More Information on Patching
+
+The @ref primerpatches provides a more complete guide to creating,
+managing, and contributing patches to the OpenOCD project.
+
+ */
+/** @file
+This file contains the @ref patchguide page.
+*/

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 84bdb3c470f8e34e8def56bc59acd9e99ba1d31e..2e0143edff4db78b7af7e91cf1ff938c08cd6621 100644 (file)
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -223,7 +223,7 @@ communication between developers:
 @uref{https://lists.berlios.de/mailman/listinfo/openocd-development}
 
 Discuss and submit patches to this list.
-The @file{PATCHES} file contains basic information about how
+The @file{PATCHES.txt} file contains basic information about how
 to prepare patches.
 
 

diff --git a/tools/release.sh b/tools/release.sh
index c464c49f72f0dabf6961199d7db6b10230e41996..12dfdb6ab093ac6874832ac14323d9ec8992d83b 100755 (executable)
--- a/tools/release.sh
+++ b/tools/release.sh
@@ -205,7 +205,7 @@ For older NEWS, see the NEWS files associated with each release
 
 For more information about contributing test reports, bug fixes, or new
 features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES files in the source archive).
+the BUGS and PATCHES.txt files in the source archive).
 NEWS
        git add NEWS