summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorSimon Howard2011-03-28 23:48:31 +0000
committerSimon Howard2011-03-28 23:48:31 +0000
commit0268c882d96942175f1c6028c636dddce8af593f (patch)
treee89de4865cc0f39e6fa41ca3194906a8e580b6fa /README
parent5a2bbe2e13a02167643c93fd1840f068ce5f72f2 (diff)
downloadchocolate-doom-0268c882d96942175f1c6028c636dddce8af593f.tar.gz
chocolate-doom-0268c882d96942175f1c6028c636dddce8af593f.tar.bz2
chocolate-doom-0268c882d96942175f1c6028c636dddce8af593f.zip
Remove the BUGS file as it doesn't really contain any useful
information. Subversion-branch: /trunk/chocolate-doom Subversion-revision: 2316
Diffstat (limited to 'README')
-rw-r--r--README9
1 files changed, 5 insertions, 4 deletions
diff --git a/README b/README
index dbc26b7f..f641c126 100644
--- a/README
+++ b/README
@@ -65,10 +65,11 @@ Here are some examples:
You are encouraged to sign up and contribute any useful information
you may have regarding the port!
- * Chocolate Doom is not perfect. See the BUGS file for a list of
- known issues. Because of the nature of the project, you may also
- encounter Vanilla Doom bugs; these are intentionally present; see
- the NOT-BUGS file for more information.
+ * Chocolate Doom is not perfect. Although it aims to accurately
+ emulate Vanilla Doom, some of the behavior of Vanilla Doom can be
+ very difficult to reproduce. Because of the nature of the project,
+ you may also encounter Vanilla Doom bugs; these are intentionally
+ present; see the NOT-BUGS file for more information.
New bug reports can be submitted to the Chocolate Doom bug tracker
on Sourceforge. See: