Commit 6f82a6d0 authored by Nick Roberts's avatar Nick Roberts

*** empty log message ***

parent 2462bc66
...@@ -10,7 +10,7 @@ the Emacs distribution, the Emacs web pages also contain much ...@@ -10,7 +10,7 @@ the Emacs distribution, the Emacs web pages also contain much
information. information.
You may also want to submit your change so that can be considered for You may also want to submit your change so that can be considered for
conclusion in a future version of Emacs (see below). inclusion in a future version of Emacs (see below).
If you don't feel up to hacking Emacs, there are still plenty of ways to If you don't feel up to hacking Emacs, there are still plenty of ways to
help! You can answer questions on the mailing lists, write help! You can answer questions on the mailing lists, write
...@@ -23,7 +23,8 @@ work in progress. ...@@ -23,7 +23,8 @@ work in progress.
Ref: http://www.gnu.org/software/emacs/ Ref: http://www.gnu.org/software/emacs/
Finally, there are certain legal requirements and style issues which Finally, there are certain legal requirements and style issues which
all contributors need to be aware of. all contributors need to be aware of:
o Coding Standards o Coding Standards
...@@ -34,6 +35,7 @@ o Coding Standards ...@@ -34,6 +35,7 @@ o Coding Standards
Emacs has certain additional coding requirements. Emacs has certain additional coding requirements.
Ref: http://www.gnu.org/prep/standards_toc.html Ref: http://www.gnu.org/prep/standards_toc.html
Ref: Standards Info Manual
o Copyright Assignment o Copyright Assignment
...@@ -41,15 +43,12 @@ o Copyright Assignment ...@@ -41,15 +43,12 @@ o Copyright Assignment
Before we can accept code contributions from you, we need a Before we can accept code contributions from you, we need a
copyright assignment form filled out and filed with the FSF. copyright assignment form filled out and filed with the FSF.
See some documentation by the FSF for details and contact us Contact us via the Emacs mailing list to obtain the relevant
via the Emacs mailing list to obtain the relevant
forms. forms.
Small changes can be accepted without a copyright assignment Small changes can be accepted without a copyright assignment
form on file. form on file.
Ref: http://www.gnu.org/prep/maintain.html#SEC6
o Getting the Source Code o Getting the Source Code
...@@ -57,7 +56,7 @@ o Getting the Source Code ...@@ -57,7 +56,7 @@ o Getting the Source Code
from the Savannah web site. It is important that you submit from the Savannah web site. It is important that you submit
your patch using this version, as any bug in a released version your patch using this version, as any bug in a released version
of Emacs may already be fixed. It also makes it easier for of Emacs may already be fixed. It also makes it easier for
others to test your patch, others to test your patch.
Ref: http://savannah.gnu.org/projects/emacs Ref: http://savannah.gnu.org/projects/emacs
...@@ -76,34 +75,35 @@ o Submitting Patches ...@@ -76,34 +75,35 @@ o Submitting Patches
A ChangeLog entry as plaintext (separate from the patch); see A ChangeLog entry as plaintext (separate from the patch); see
the various ChangeLog files for format and content. Note that, the various ChangeLog files for format and content. Note that,
unlike some other projects, we do require ChangeLogs also for unlike some other projects, we do require ChangeLogs also for
documentation (i.e., .texi files). documentation i.e. texinfo files.
Ref: Change Log Concepts node of the Standards Info Manual
The patch itself. If you are accessing the CVS repository use The patch itself. If you are accessing the CVS repository use
"cvs update; cvs diff -cp"; else, use "diff -cp OLD NEW" or "cvs update; cvs diff -cp"; else, use "diff -cp OLD NEW". If
"diff -up OLD NEW". If your version of diff does not support your version of diff does not support these options, then get
these options, then get the latest version of GNU diff. the latest version of GNU diff.
We accept patches as plain text (preferred for the compilers We accept patches as plain text (preferred for the compilers
themselves), MIME attachments (preferred for the web pages), themselves), MIME attachments (preferred for the web pages), or
or as uuencoded gzipped text. as uuencoded gzipped text.
When you have all these pieces, bundle them up in a mail message When you have all these pieces, bundle them up in a mail message
and send it to emacs-pretest-bug@gnu.org or emacs-devel@gnu.org. and send it to emacs-pretest-bug@gnu.org or emacs-devel@gnu.org.
All patches and related discussion should be sent to the All subsequent discussion should also be sent to the mailing
emacs-pretest-bug mailinglist. list.
o Please read your patch before submitting it. o Please read your patch before submitting it.
A patch containing several unrelated changes or A patch containing several unrelated changes reformats will be
arbitrary reformats will be returned with a request returned with a request to send them separately.
to re-formatting / split it.
o Supplemental information for Emacs Developers: o Supplemental information for Emacs Developers:
If you wish to contribute to Emacs on a regular basis then If you wish to contribute to Emacs on a regular basis then you
you may be given write access to the CVS repository. may be given write access to the CVS repository.
Discussion about Emacs development takes place on Discussion about Emacs development takes place on
emacs-devel@gnu.org. emacs-devel@gnu.org.
...@@ -113,8 +113,8 @@ o Supplemental information for Emacs Developers: ...@@ -113,8 +113,8 @@ o Supplemental information for Emacs Developers:
add an item to the NEWS file. add an item to the NEWS file.
The best way to understand Emacs Internals is to read the code The best way to understand Emacs Internals is to read the code
but there is also a node "GNU Emacs Internals" in the Appendix but the nodes "Tips" and "GNU Emacs Internals" in the Appendix
of the Emacs Lisp Reference Manual that may help. of the Emacs Lisp Reference Manual may also help.
The file DEBUG describes how to debug Emacs. The file DEBUG describes how to debug Emacs.
......
2006-07-04 Nick Roberts <nickrob@snap.net.nz>
* CONTRIBUTE: New file.
2006-06-25 Kim F. Storm <storm@cua.dk> 2006-06-25 Kim F. Storm <storm@cua.dk>
* AUTHORS: Regenerate. * AUTHORS: Regenerate.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment