-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
Document file system object content addressing #10479
Conversation
4706b5e
to
d5b583d
Compare
Oh woops --- I will still heavily rewriting "nix archive" and below in the new page. (The current material therein is recycled from #6877 and, in some cases, transitively, Eelco's thesis.) I'll still incorporate these suggestions in the next draft, however! |
0a6c547
to
51d3977
Compare
51d3977
to
93a0742
Compare
93a0742
to
05c90bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will try to do a single large review next time instead of batches.
"Refresh" notification made me submit earlier (by choice).
@@ -10,16 +10,28 @@ namespace nix { | |||
/** | |||
* An enumeration of the ways we can serialize file system | |||
* objects. | |||
* | |||
* See `file-system-object/content-address.md#serial` in the manual for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thought:
I've linked to the unstable
manual URL before in the external API docs, but we might want to weigh that differently for internal docs.
In addition: - Take the opportunity to add a bunch more missing hyperlinks, too. - Remove some glossary entries that are now subsumed by dedicated pages. We used to not be able to do this without breaking link fragments, but now we can, so pick up where we left off. Co-authored-by: Robert Hensing <[email protected]>
Motivation
Trying to document the store model from the ground up. This is the next step. More things to be taken from #6877 come after.
Context
The git hashing work (#8919) has resulted in this code getting cleaned up and there being more than two cases (so bools don't suffice).
Now is a good time to shore up the docs accordingly.
Also prepares for #10480
Priorities and Process
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.