empire/empserver
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update documentation to talk about git instead of CVS

Browse source
This commit is contained in:
Markus Armbruster 2008-03-28 20:42:49 +01:00
parent 2f5cad1997
commit a7cf600abc
4 changed files with 13 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README
View file

@ -20,8 +20,8 @@ To build the server and set up a game, follow the steps below.
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

2
bootstrap
View file

@ -1,5 +1,5 @@
#!/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

12
doc/coding
View file

@ -422,14 +422,18 @@ There are several ways to access an object in set FOO:
writebmap() instead.
CVS
git
---
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

2
src/client/README
View file

@ -12,7 +12,7 @@ the Free Software Foundation; either version 2 of the License (in file
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;