Mikhail Glushenkov authored 8 years ago and Edward Z. Yang committed 8 years ago

It wasn't clear what "three-year support window for cabal-install"
means re: self-upgrade.

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

7.2.2 was released on Nov 11 2011, so we don't have to support it in
the 2.0 release.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

For some reason github is finicky when it comes to local links. Also,
I'm dyslexic it seems when it comes to Markdown's link syntax.

* Reformat tests/README, add links to individual files.
* Add link to tests/README to HACKING.
* Add links to license files.

* Attempt to fix local links.
* Experiment with syntax highlighting.
* Add title to HACKING.
* Reword an awkward sentence and a few wordy headings.
* Change "Unix" to "Unix-like".

* Rename README files to README.md and link from root.
* Rename HACKING to HACKING.md and link from root.
* Add additional links.
* A fair amount of added punctuation and rewording.
* Replace references to darcs/trac with git/github.

Makes things a little simpler in GHC's build system if libraries are in
the same directory as their name.

At the top level we now have cabal/ and cabal-install/