Submissions which do not conform to the standards will be
returned with a request to reformat the changes.
+ Ref: http://www.gnu.org/prep/standards_toc.html
+
GDB has certain additional coding requirements. Those
- requirements are explained in the GDB internals documentation
- in the gdb/doc directory.
+ requirements are explained in the GDB internals documentation.
- Ref: http://www.gnu.org/prep/standards_toc.html
+ Ref: http://sourceware.org/gdb/wiki/Internals%20Coding-Standards
o Copyright Assignment
unlike some other projects, we do require ChangeLogs also for
documentation (i.e., .texi files).
- The patch itself. If you are accessing the CVS repository use
- "cvs update; cvs diff -cp"; else, use "diff -cp OLD NEW" or
- "diff -up OLD NEW". If your version of diff does not support
- these options, then get the latest version of GNU diff.
+ The patch itself. If you are accessing the git repository, use
+ "git diff", remembering first to update to the current master;
+ else, use "diff -up OLD NEW". If your version of diff does not
+ support these options, then get the latest version of GNU diff.
We accept patches as plain text (preferred for the compilers
themselves), MIME attachments (preferred for the web pages),
message and send it to gdb-patches@sourceware.org. All
patches and related discussion should be sent to the
gdb-patches mailinglist. For further information on the GDB
- CVS repository, see the Anonymous read-only CVS access and
- Read-write CVS access page.
+ git repository, see the Anonymous read-only git access and
+ Read-write git access page.
--
``configure''.
The maintainer will re-generate those files
- using autoconf (2.59 as of 2005-01-07).
+ using autoconf (2.64 as of 2009-08-22).
o If ``gdb/gdbarch.sh'' is modified, you don't
Fix PR gdb/4705.
The text ``PR gdb/4705'' should also be included
- in the CVS commit message. That causes the
+ in the git commit message. That causes the
patch to automatically be archived with the PR.