eUgEntOptIc44/gitoxide
1
1
Fork 0
mirror of https://github.com/Byron/gitoxide synced 2025-10-06 01:52:40 +02:00
Code Issues Activity

Merge pull request #2137 from tmm1/typo-fix

Browse Source 
Fix typo
This commit is contained in:
Sebastian Thiel
2025-08-26 19:53:59 +02:00
committed by GitHub
parent 677de22140 8e451cfff1
commit ad1e2ed9ce
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Cargo.toml
View File

@@ -109,7 +109,7 @@ prodash-render-tui = ["prodash/render-tui", "prodash/render-tui-crossterm", "gix
prodash-render-line = ["prodash/render-line", "prodash-render-line-crossterm", "gix/progress-tree"]
## Prints statistical information to inform about cache efficiency when those are dropped.
## Use this as a way to understand if bigger caches actually produce greater yiedls.
## Use this as a way to understand if bigger caches actually produce greater yields.
cache-efficiency-debug = ["gix-features/cache-efficiency-debug"]
## A way to enable most `gitoxide-core` tools found in `ein tools`, namely `organize` and `estimate hours`.

2
gix/src/lib.rs
View File

@@ -37,7 +37,7 @@
//! to understand which cache levels exist and how to leverage them.
//!
//! When accessing an object, the first cache that's queried is a memory-capped LRU object cache, mapping their id to data and kind.
//! It has to be specifically enabled a [`Repository`].
//! It has to be specifically enabled on a [`Repository`].
//! On miss, the object is looked up and if a pack is hit, there is a small fixed-size cache for delta-base objects.
//!
//! In scenarios where the same objects are accessed multiple times, the object cache can be useful and is to be configured specifically