Expand description
A crate for handling the references stored in various formats in a git repository.
References are also called refs which are used interchangeably.
Refs are the way to keep track of objects and come in two flavors.
- symbolic refs are pointing to another reference
- peeled refs point to the an object by its
ObjectId
They can be identified by a relative path and stored in various flavors.
- files
- loose
- one reference maps to a file on disk
- packed
- references are stored in a single human-readable file, along with their targets if they are symbolic.
- loose
§Feature Flags
serde
— Data structures implementserde::Serialize
andserde::Deserialize
.
Re-exports§
pub use gix_object::bstr;
Modules§
- Transactions are the only way make changes to the ref store in order to increase the chance of consistency in a multi-threaded environment.
Structs§
- A validated complete and fully qualified reference name, safe to use for all operations.
- A validated complete and fully qualified reference name, safe to use for all operations.
- A validated prefix for references to act as a namespace.
- A validated and potentially partial reference name, safe to use for common operations.
- A validated and potentially partial reference name, safe to use for common operations.
- A fully owned backend agnostic reference