adam/cobm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updating bugzilla URL.

Browse Source 
git-svn-id: svn://svn.code.sf.net/p/sc2/code/trunk@2455 8092fc87-c524-0410-9efc-e669fe64eaf9
This commit is contained in:
meep-eep
2006-10-24 02:11:54 +00:00
parent d7b1b23022
commit 34476cdf86
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sc2/BUGS
+1 -1
View File
@@ -1,5 +1,5 @@
All known bugs and missing features are listed in our online bug database, All known bugs and missing features are listed in our online bug database,
which can be found at which can be found at
http://uqm.stack.nl/bugs/ http://bugs.uqm.stack.nl/
New bugs that you may find can be reported at the same location. New bugs that you may find can be reported at the same location.
sc2/Contributing
+1 -1
View File
@@ -6,7 +6,7 @@ These guidelines are there so that you won't waste both our and your time.
Before making changes: Before making changes:
- Read this entire document - Read this entire document
- See if the the Bugzilla bug database at - See if the the Bugzilla bug database at
http://uqm.stack.nl/bugs/ contains any comments on what you're planning http://bugs.uqm.stack.nl/ contains any comments on what you're planning
to do. to do.
- Make sure you're using the most recent cvs version - Make sure you're using the most recent cvs version
- Discuss in advance what you're planning to do, with the core team. - Discuss in advance what you're planning to do, with the core team.
sc2/doc/users/manual.txt
+1 -1
View File
@@ -206,7 +206,7 @@ we'd like you to report it, but before you do, please do the following:
is produced; if the game hangs, check to see if the game-exit key is produced; if the game hangs, check to see if the game-exit key
(F12) works. (F12) works.
- Go to the bug database at http://uqm.stack.nl/cgi-bin/bugs/index.cgi - Go to the bug database at http://bugs.uqm.stack.nl/
and post a report of the problem there. Search the database first if and post a report of the problem there. Search the database first if
it has been already posted; if we get many duplicate reports, processing it has been already posted; if we get many duplicate reports, processing
them eats our time from actual development. If it's been reported, and them eats our time from actual development. If it's been reported, and