If you downloaded a tarball, unpack it.
- If you're pulling from CVS, check out and run bootstrap. This
- requires recent versions of Autoconf and Automake to be installed.
+ If you cloned a git repository, run bootstrap. This requires
+ recent versions of Autoconf and Automake to be installed.
(2) Building a server
#!/bin/sh -e
-# Run this script after a fresh CVS checkout to bring the source tree
+# Run this script after a fresh git-clone to bring the source tree
# into a state where you can run configure.
aclocal -I m4
autoconf
writebmap() instead.
-CVS
+git
---
-Commit related changes together, unrelated changes separately.
+Commit related changes together, unrelated changes separately.
-See chapter Change Logs in the GNU coding standards for guidelines on
-log messages. Try http://www.gnu.org/prep/standards_40.html#SEC40 or
-search the web for `gnu coding standards change logs'.
+Write meaningfull commit messages. Start with a single short line
+(ideally less than 50 characters) summarizing the change, followed by
+a blank line and then a more thorough description.
+
+The purpose of the change log is not to explain how the code works;
+that should be done in the source code itself. It's to explain *why*
+you made the change, and what is affected by it.
Don't change whitespace gratuitiously, say just because your editor
screws up tabs. Such changes make it much harder to figure out who
The client is distributed as part of the complete source tarball and
as a standalone client tarball. The instructions below apply to the
client tarball. If you got the complete source, as tarball or from
-CVS, refer to ../../README instead.
+a git repository, refer to ../../README instead.
See file `INSTALL' for detailed compilation and installation
instructions. Quick guide for the impatient: run configure; make;