X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fintro.xml;h=e0ef1237d31dfe49c27126eb66b58a80e03ae0c2;hb=0093a2827f6b4007c4fcb298a559c9b7dd17aec1;hp=7216942f1e7b00bf883f9199e0a6867c0a209144;hpb=147c8d2ec47fab14fd0386e10e73f1a4da005442;p=ghc-hetmet.git
diff --git a/docs/users_guide/intro.xml b/docs/users_guide/intro.xml
index 7216942..e0ef123 100644
--- a/docs/users_guide/intro.xml
+++ b/docs/users_guide/intro.xml
@@ -41,8 +41,7 @@
call-graph like structure. See for more
details.
- GHC comes with a large collection of libraries, with
- everything from parser combinators to networking. The libraries are
+ GHC comes with a number of libraries. These are
described in separate documentation.
@@ -83,7 +82,7 @@
This list is for GHC users to chat among themselves.
If you have a specific question about GHC, please check the
FAQ
+ url="http://haskell.org/haskellwiki/GHC/FAQ">FAQ
first.
@@ -121,55 +120,13 @@
- glasgow-haskell-bugs:
-
- Send bug reports for GHC to this address! The sad and
- lonely people who subscribe to this list will muse upon
- what's wrong and what you might do about it.
-
-
-
- list email address:
-
- glasgow-haskell-bugs@haskell.org
-
-
-
-
- subscribe at:
-
- http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs.
-
-
-
-
- admin email address:
-
- glasgow-haskell-bugs-admin@haskell.org
-
-
-
-
- list archives:
-
- http://www.haskell.org/pipermail/glasgow-haskell-bugs/
-
-
-
-
-
-
-
cvs-ghc:
The hardcore GHC developers hang out here. This list
- also gets commit message from the CVS repository. There are
- several other similar lists for other parts of the CVS
- repository (eg. cvs-hslibs,
- cvs-happy, cvs-hdirect
- etc.)
+ also gets commit message from the GHC darcs repository. There are
+ other lists for other darcs
+ repositories (most notably cvs-libraries).
+
@@ -223,96 +180,13 @@
reporting bugs
- Glasgow Haskell is a changing system so there are sure to be
- bugs in it.
+
+ Glasgow Haskell is a changing system so there are sure to be
+ bugs in it. If you find one, please see
+ this wiki page
+ for information on how to report it.
+
- To report a bug, either:
-
-
-
- Preferred: Create
- a new bug, and enter your bug report. You can also
- search the bug database here to make sure your bug hasn't already
- been reported (if it has, it might still help to add information
- from your experience to the existing report).
-
-
- Bug reports can also be emailed to
- glasgow-haskell-bugs@haskell.org.
-
-
-
-
- How do I tell if I should report my bug?
-
- Take a look at the FAQ and , which will give you some guidance as to
- whether the behaviour you're seeing is really a bug or
- not.
-
- If it is a bug, then it might have been reported before:
- try searching on the bug tracker,
- and failing that, try Google.
-
- If in doubt, just report it.
-
-
-
- What to put in a bug report
- bug reportscontents
-
- The name of the bug-reporting game is: facts, facts,
- facts. Don't omit them because “Oh, they won't be
- interested…”
-
-
-
- What kind of machine are you running on, and exactly
- what version of the operating system are you using? (on a
- Unix system, uname -a or cat
- /etc/motd will show the desired information.) In
- the bug tracker, this information can be given in the
- “Architecture” and “Operating
- system” fields.
-
-
-
- What version of GCC are you using? gcc -v will tell you.
-
-
-
- Run the sequence of compiles/runs that caused the
- offending behaviour, cut-and-paste the whole session into
- the bug report. We'd prefer to see the whole thing.
-
-
-
- Add the -v flag when running GHC, so we can see exactly
- what was run, what versions of things you have, etc.
-
-
-
- What is the program behaviour that is wrong, in your
- opinion?
-
-
-
- If practical, please attach or send enough source
- files for us to duplicate the problem.
-
-
-
- If you are a Hero and track down the problem in the
- compilation-system sources, please send us patches (either
- darcs send, plain patches, or just whole
- files if you prefer).
-
-
-