summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorSimon Howard2013-12-06 03:48:25 +0000
committerSimon Howard2013-12-06 03:48:25 +0000
commitb662a3d8e84ca176b82406dbc4c28075413eb9d9 (patch)
treeca856d1a5d884d9ab04e3c65789aa907d1254a3c /README
parent89fa06e5402c4a0d4a288503ce8d41d4dfa59cb7 (diff)
downloadchocolate-doom-b662a3d8e84ca176b82406dbc4c28075413eb9d9.tar.gz
chocolate-doom-b662a3d8e84ca176b82406dbc4c28075413eb9d9.tar.bz2
chocolate-doom-b662a3d8e84ca176b82406dbc4c28075413eb9d9.zip
Update README to point at Github instead of Sourceforge. Remove contents
of ChangeLog and just give instructions to use the Git repository on Github. Subversion-branch: /branches/v2-branch Subversion-revision: 2759
Diffstat (limited to 'README')
-rw-r--r--README5
1 files changed, 2 insertions, 3 deletions
diff --git a/README b/README
index cc314366..905e3c7c 100644
--- a/README
+++ b/README
@@ -74,10 +74,9 @@ Here are some examples:
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:
+ New bug reports can be submitted to the issue tracker on Github:
- http://sourceforge.net/projects/chocolate-doom
+ https://github.com/fragglet/chocolate-doom/issues
* Source code patches are welcome, but please follow the style
guidelines - see the file named HACKING included with the source