Skip to content
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

fix: avoid unintended bold text in Building ZFS.rst #492

Merged
merged 1 commit into from
Feb 12, 2024
Merged

fix: avoid unintended bold text in Building ZFS.rst #492

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
6 changes: 3 additions & 3 deletions docs/Developer Resources/Building ZFS.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,12 @@ git repository for the project is the `zfs

There are two main components in this repository:

- **ZFS**: The ZFS repository contains a copy of the upstream OpenZFS
- **ZFS**: The ZFS repository contains a copy of the upstream OpenZFS
code which has been adapted and extended for Linux and FreeBSD. The
vast majority of the core OpenZFS code is self-contained and can be
used without modification.

- **SPL**: The SPL is a thin shim layer which is responsible for
- **SPL**: The SPL is a thin shim layer which is responsible for
implementing the fundamental interfaces required by OpenZFS. It's
this layer which allows OpenZFS to be used across multiple
platforms. SPL used to be maintained in a separate repository, but
Expand Down Expand Up @@ -74,7 +74,7 @@ depends on your requirements.
downside to using packages it is greatly increases the time required
to build, install, and test a change.

- **In-tree**: Development can be done entirely in the SPL/ZFS source
- **In-tree**: Development can be done entirely in the SPL/ZFS source
tree. This speeds up development by allowing developers to rapidly
iterate on a patch. When working in-tree developers can leverage
incremental builds, load/unload kernel modules, execute utilities,
Expand Down
Loading