aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.devel
diff options
context:
space:
mode:
authorGravatar David Aspinall <da@inf.ed.ac.uk>2000-05-09 16:13:23 +0000
committerGravatar David Aspinall <da@inf.ed.ac.uk>2000-05-09 16:13:23 +0000
commit73358744b37293cea04fcf0c29a127aba7d654f2 (patch)
tree805cf32a5438d0d1afa51327c6a5e13e339e2021 /README.devel
parentf5e27f6de5b2e2e1b68239894014c465ccb4790a (diff)
Updated
Diffstat (limited to 'README.devel')
-rw-r--r--README.devel15
1 files changed, 12 insertions, 3 deletions
diff --git a/README.devel b/README.devel
index 58c44509..1f280c8d 100644
--- a/README.devel
+++ b/README.devel
@@ -35,6 +35,8 @@ When writing your modes, please follow the Emacs Lisp Conventions
See the Emacs Lisp reference manual, node Style Tips.
+
+
** Standards for each instance of PG
We include a README file and low-level todo file for each prover.
@@ -54,11 +56,13 @@ maintaining compatibility across different versions of Emacs.
XEmacs is the primary development (and use) platform, but we'd like to
maintain compatibility with FSF Emacs, and the Japanicised versions of
-that.
+that. The development policy is for the main codebase to be written
+for the latest stable version of XEmacs. We follow XEmacs advice on
+removing obsolete function calls.
Hopefully one day we may have a proper test suite and mechanism to
-test across different versions of Emacs. For the time being, be care
-of the following tips (gathered from experience).
+test across different versions of Emacs. For the time being, be
+careful of the following tips (gathered from experience).
*** Common Lisp macros -- Japan Emacsen have older versions
@@ -71,3 +75,8 @@ of the following tips (gathered from experience).
*** Moving to new branch.
find * -path '*/CVS' -prune -o -path 'CVS' -prune -o -print | xargs cvs commit -m"Updating branch" -f -r 4.0
+
+
+*** Making a new branch.
+
+ See etc/cvs-tips.txt