Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
alexbiehl-gc
GHC
Commits
3d55cb1e
Commit
3d55cb1e
authored
27 years ago
by
Simon Marlow
Browse files
Options
Downloads
Patches
Plain Diff
[project @ 1998-02-25 15:59:43 by simonm]
remove references to hslibs.
parent
6c01550d
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CVS-CHEAT-SHEET
+6
-6
6 additions, 6 deletions
CVS-CHEAT-SHEET
with
6 additions
and
6 deletions
CVS-CHEAT-SHEET
+
6
−
6
View file @
3d55cb1e
...
...
@@ -51,15 +51,15 @@ Using CVS for the First Time
tree you'll be working on. The directory structure looks like this:
fptools/ghc GHC
fptools/hslibs Haskell Libraries
fptools/happy Happy
fptools/haggis Haggis
fptools/green-card Green Card
fptools/nofib Nofib test suite
fptools/hdirect IDL-to-Haskell compiler
fptools/common-rts GHC/Hugs combined run-time system
For each directory, there's a mailing list: fp-cvs-ghc,
fp-cvs-
hsl
ib
s
etc. Everyone on the mailing list is sent a message
fp-cvs-
nof
ib etc. Everyone on the mailing list is sent a message
automatically by CVS whenever someone checks in a change, this helps
to keep track of what's going on when several people are working on
related stuff. Ask the CVS meister to put you on the relevant
...
...
@@ -100,11 +100,11 @@ Checking Out a Source Tree
You can call the fptools directory whatever you like, CVS won't mind.
$ cd <directory>
$ cvs checkout ghc
hslibs
happy
$ cvs checkout ghc happy
The second command here checks out the relevant modules you want to
work on. For a GHC build, for instance, you need at least
ghc and
hslibs
.
work on. For a GHC build, for instance, you need at least
the ghc
module (in fact you can get away with just that)
.
Committing Your Changes
...
...
@@ -195,7 +195,7 @@ General Hints
* To check out extra bits into an already-checked-out tree, use the
following procedure. Suppose you have a checked-out fptools tree containing
just ghc
and hslibs
, and you want to add nofib to it:
just ghc, and you want to add nofib to it:
cd fptools
cvs checkout nofib
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment