emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] master ed2e7e2: Mention CONTRIBUTE in README


From: Xue Fuqiao
Subject: [Emacs-diffs] master ed2e7e2: Mention CONTRIBUTE in README
Date: Sat, 14 Nov 2015 05:03:52 +0000

branch: master
commit ed2e7e20ae0945288c98091f308f5460c3453873
Author: Xue Fuqiao <address@hidden>
Commit: Xue Fuqiao <address@hidden>

    Mention CONTRIBUTE in README
    
    Mention CONTRIBUTE in README, since it was moved from etc/ to root.
    * etc/TODO: Remove the reference to `etc/CONTRIBUTE'.
    * README: Mention CONTRIBUTE.
---
 README   |    3 +++
 etc/TODO |    9 ++++++---
 2 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/README b/README
index be99852..1f3de15 100644
--- a/README
+++ b/README
@@ -15,6 +15,9 @@ user-visible changes in recent versions of Emacs.
 The file etc/PROBLEMS contains information on many common problems that
 occur in building, installing and running Emacs.
 
+The file CONTRIBUTE contains information on contributing to Emacs as a
+developer.
+
 You may encounter bugs in this release.  If you do, please report
 them; your bug reports are valuable contributions to the FSF, since
 they allow us to notice and fix problems on machines we don't have, or
diff --git a/etc/TODO b/etc/TODO
index 946a4fe..7045731 100644
--- a/etc/TODO
+++ b/etc/TODO
@@ -13,9 +13,12 @@ the latest version of this file in the Emacs source code 
repository.
 
 Since Emacs is an FSF-copyrighted package, please be prepared to sign
 legal papers to transfer the copyright on your work to the FSF.
-For more details on this, see the section "Copyright Assignment"
-in etc/CONTRIBUTE.  That file also contains some more practical
-details about getting involved.
+Copyright assignment is a simple process.  Residents of some countries
+can do it entirely electronically.  We can help you get started, and
+answer any questions you may have (or point you to the people with the
+answers), at the address@hidden mailing list.
+
+For more information about getting involved, see the CONTRIBUTE file.
 
 As well as the issues listed here, there are bug reports at
 <http://debbugs.gnu.org>.  Bugs tagged "easy" ought to be suitable for



reply via email to

[Prev in Thread] Current Thread [Next in Thread]