Take format specification history back to Cabal-1.0 #10847
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mpilgrem
force-pushed
the
to-spec-origin
branch
6 times, most recently
from
1cec7c8 to
d8af336
Compare
geekosaur
approved these changes
Mar 26, 2025
mpilgrem
force-pushed
the
to-spec-origin
branch
from
d8af336 to
e8a0e71
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The motivation is that the documentation of the history of the format specification is almost complete (it currently stops at Cabal 1.8). This will complete it.
Some background to early Cabal version numbering is available here.
The format specification appears to have been stable between Cabal 1.2.1 and Cabal 1.6.
This PR does not modify behaviour or interface
Not applicable, but aims to be consistent with existing text.
Not applicable.