Skip to content

silly commit #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

silly commit #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions HACKING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,8 @@ identical; only the first two steps are different:
because we have to use the `cabal-install` sandbox, not the Cabal one. If you
use the relative path, you are set.)

blah, blah

Copy link
Owner Author

@mtullsen mtullsen Mar 9, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wherefore blah? ...

Coding Conventions
------------------

Expand All @@ -144,8 +146,13 @@ respected. In general, try to adhere to [this style guide][guide].
Dependencies policy
-------------------

Cabal's policy is to support being built by versions of GHC that are up
to 3 years old.
blah, blah
blah, blah
blah, blah
blah, blah
blah, blah
blah, blah


The Cabal library must be buildable out-of-the-box, i.e., the
dependency versions required by Cabal must have shipped with GHC for
Expand Down