Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

This repository is no longer used for development of the GHC I/O

manager

Updated the README to point future contributors to the GHC base
library.
  • Loading branch information...
commit 2ca43e49327aa7854396b800ff4184d8b00a69f0 1 parent 0273c61
Johan Tibell authored
Showing with 6 additions and 66 deletions.
  1. +6 −66 README.md
View
72 README.md
@@ -7,71 +7,11 @@ handles, sockets, timers, etc.
Contributing
------------
-### Prerequisites
+The event library has been merged into the main GHC tree and this
+repository only exists preserve the project history. If you want to
+modify the event manager you can do so by checking out the base
+library
-Make sure you read the [Haskell Style Guide] [1].
+ darcs get --lazy http://darcs.haskell.org/libraries/base
-The existing code doesn't follow the style guide fully but you should
-follow it for all new code.
-
-### Creating patches
-
-The preferred way of contributing changes to the project is to use Git
-and send the patches over email using the Git commands `format-patch`
-and `send-email`. Step by step instructions:
-
-Clone the repository:
-
- git clone http://github.com/tibbe/event
-
-Make your changes:
-
- cd event
- $EDITOR <file>
-
-Commit your changes in one or more commits:
-
- git add <file>
- git commit
-
-Make sure you write a good commit message. Commit messages should
-contain a short summary on a separate line and, if needed, a more
-thorough explanation of the change. Write full sentences and use
-proper spelling, punctuation, and grammar. See
-[A Note About Git Commit Messages] [2] for more information.
-
-You might want to use `git rebase` to make sure your commits
-correspond to nice, logical commits. Make sure whitespace only
-changes are kept in separate commits to ease reviewing.
-
-To prepare your patches for sending:
-
- git format-patch -n origin
-
-This will create one patch file per patch.
-
- git send-email --to <maintainer> <patch files>
-
-The maintainer is specified in the Cabal file. The maintainer will
-review your patches and may ask you to make changes to them. Make the
-changes in your local repository and use `git rebase` to massage them
-into nice, logical commits and resend the patches.
-
-Building and running the tests
-------------------------------
-
-The configure script and several of the include files are generated
-using autotools. The first time you build the library you have to
-run:
-
- autoreconf
-
-You can build and run all unit tests by running:
-
- cabal configure && cabal build && make -C tests run-tests
-
-References
-----------
-
-[1]: http://github.com/tibbe/haskell-style-guide
-[2]: http://www.tpope.net/node/106
+and changing the code under `System.Event`.
Please sign in to comment.
Something went wrong with that request. Please try again.