NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #1385 most downloaded on crates.io
A crate of the gitoxide project
Latest stable
0.64.0
Last release 1 months ago
22 Oct 2026
Ships on a steady schedule
a new release about every 4 weeks
Nearly every release is documented
notes for 52 of 52 stable releases
1 version withdrawn
withdrawn after publishing
4 years old
53 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
retry the current commit when graph parents are corrupt
retry the current commit when graph parents are corrupt
Both Simple traversal paths pop the current commit before decoding its
cached parents. If parent iteration fails, dropping the cache and recursively
requesting the next commit skips the popped commit and its entire ancestry.
With an out-of-range inline parent, a two-commit gix revision walk could
therefore succeed with an empty result.
Put the current commit back at the front of the topology queue or into the
date queue with its existing priority, then continue the loop after disabling
the cache. The object database retries that same commit without recursion;
any object lookup or decoding failure is still propagated.
The regression corrupts a disposable graph, confirms that Git rejects it,
and checks that the existing gix fallback policy preserves both commits
across breadth-first traversal, both date orders, cutoff sorting, and
first-parent traversal.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
5 commits contributed to the release over the course of 13 calendar days.
allow configuring the reqwest HTTP client
allow configuring the reqwest HTTP client
Applications need to supply a custom TLS configuration, including an explicit
cryptographic provider, before reqwest builds its HTTP client. The existing
request callback runs too late to configure that client.
Add reqwest::Options::configure_client and build the client lazily when the
first request makes the HTTP options available. Reuse that client for later
requests, retaining the configured options if a failed worker is restarted.
Apply Git's redirect policy after customization so the callback cannot replace
its safeguards for configured request headers or unsafe redirects.
Adding this public option requires existing complete Options literals to
specify configure_client or use ..Default::default().
reqwest HTTP client (7111e30)Keep rust workspace tests inside disposable repositories and isolated environments
Direct Git launches inherited repository selectors and user configuration even
when tests supplied a fixture working directory. Tests of default-environment
APIs and local Git transports also shared the runner's environment. A few
journey tests wrote beneath source directories or used the source checkout as
the repository under test.
Use the shared gix-testtools Git command builder for subprocess setup, isolated
repository options for fixtures, and isolated child processes where the real
environment-reading API must be exercised. Scope CWD changes, copy the fixture
used by an object-write test, and run shell journeys through jtt run. Keep
journey worktrees and example output within their disposable sandboxes and
replace the attributes checkout test with a representative fixture repository.
Prompt examples also run in isolated children and must build successfully; the
old tests could ignore build failures and execute stale cached binaries.
The affected Rust crate suites, internal test-tool build, and max-pure journey
suite pass from a source copy without Git metadata. Signing and Git-daemon
checks use only disposable keys, repositories, and local sockets.
migrate errors to gix-error
rubberstamp
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
<csr-id-4e0f8ff9b920e75d9554eb58c76e396e50502346/> Keep rust workspace tests inside disposable repositories and isolated environments <!-- agent --> Direct Git launches inherited repository selectors and user configuration even when tests supplied a fixture working directory. Tests of default-environment APIs and local Git transports also shared the runner's environment. A few journey tests wrote beneath source directories or used the source checkout as the repository under test.
Use the shared gix-testtools Git command builder for subprocess setup, isolated
repository options for fixtures, and isolated child processes where the real
environment-reading API must be exercised. Scope CWD changes, copy the fixture
used by an object-write test, and run shell journeys through jtt run. Keep
journey worktrees and example output within their disposable sandboxes and
replace the attributes checkout test with a representative fixture repository.
Prompt examples also run in isolated children and must build successfully; the
old tests could ignore build failures and execute stale cached binaries.
The affected Rust crate suites, internal test-tool build, and max-pure journey
suite pass from a source copy without Git metadata. Signing and Git-daemon
checks use only disposable keys, repositories, and local sockets.
<csr-id-ac0dca128afece256b9463d259fedde8c0361bb8/> migrate errors to gix-error <!-- Byron --> rubberstamp
<csr-id-4b42e0ce80ae934cae4f102f44c392581758608f/> raise MSRV to Rust 1.88
<!-- agent -->
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
37860b3)6356013)ac0dca1)c609062)4e0f8ff)a095334)4b42e0c)b8914ff)
</details>Headline benefits of this extra-curricular release are various security improvements, and greatly improved error handling and consisstency. Plumbing c
Headline benefits of this extra-curricular release are various security improvements,
and greatly improved error handling and consisstency. Plumbing crates for instance will now
use a standard std::error::Error compatible error type.
Besides that, the tracing of all commands was greatly improved.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-75f1a01ca78ac6a39f63b2c5d48fcf65b08edc43/> ignore duplicate topo traversal tips <!-- agent --> Repeated starting commits were inserted into the topological queue more than once, which could duplicate the tip and truncate walks depending on sorting. The regression compares one tip with the same tip supplied twice for both topological and date ordering, with and without a commit graph.
Ignore repeated tips at the builder boundary while preserving their first-seen order. This matches Git's duplicated-head behavior covered by t/t6003-rev-list-topo-order.sh.
commit::Info::generation
That way it's evident if a commit-graph was present for this node.
Breaking, as it adds a new public field to a structure.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
75f1a01)ebe9095)f3bbfad)gix-testtools (0cbe539)2a4d996)Store::at() where possible (17fea2a)70e98a0)4b3bf5a)commit::Info::generation (e768682)ae8845a)
</details>Headline benefits of this extra-curricular release are various security improvements, and greatly improved error handling and consisstency. Plumbing c
Headline benefits of this extra-curricular release are various security improvements,
and greatly improved error handling and consisstency. Plumbing crates for instance will now
use a standard std::error::Error compatible error type.
Besides that, the tracing of all commands was greatly improved.
remove full-screen progress mode <!-- agent --> Full-screen progress required separate command and UI threads plus channel coordination, while line progress already covers long-running commands and works with independently buffered tracing.
Remove --progress, --progress-keep-open, and the prodash-render-tui feature. Keep synchronous line progress as the only progress UI.
make trace output independently configurable <!-- Byron -->
Quick review only, as it's mostly about tracing and gix which both aren't super
important, and are seemingly working well. An extra agent-review couldn't
find anything either.
<!-- agent -->
Replace the old boolean trace switch with a bounded -t/--trace counter:
forest INFO and DEBUG at one or two occurrences, then flat DEBUG and TRACE at
three or four. Keep --threads long-only and route tracing independently of
verbose and progress rendering, including commands with bespoke execution paths
and corpus runs.
Initialize display tracing once before repository discovery, buffer it outside
prodash, and emit it after command and progress teardown. Format forest and
flat output with ANSI, then adapt the final stderr write so terminals get color
while pipes and NO_COLOR remain plain.
Corpus worker subscribers share that sink while retaining their complete
JSON trace storage, and flat modes include completed spans. gix tix remains
delegated to Tix so it installs only one subscriber.
add and remove linked worktrees from the CLI <!-- Byron -->
rubber-stamp mostly for gitoxide-core changes, did look at it though just to be sure.
Journey test was present but removed.
<!-- agent -->
The CLI previously exposed only worktree listing, despite gix supporting
both checkout and safe removal. Add worktree add (alias create) and
worktree remove using those APIs.
Creation follows Git's local-branch and detached-revision selection, including
destination-basename defaults and -b. It retains new branches after setup
failures, uses the existing listing format on success, and reports incomplete
checkouts. Removal maps repeated -f flags to dirty-worktree and lock overrides
while retaining branches.
Both commands use the existing repository, configuration, and progress options. Unsupported JSON output is rejected before mutation.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
AsHashKind (106db87)gix free index (a8e3143)<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
842bc44)cb6ec7d)c16b5a1)43ff87a)cf3053a)27aec47)1b1541e)
</details>Breaking change: gix_worktree::prepare() now accepts the destination first, followed by an add::Context containing the common Git directory and an opt…
preserve sparse-checkout state when adding worktrees
Looked at everything carefully, but was despite test refactoring, I went
through those more quickly. The benchmark I only skimmed.
Adding a linked worktree from a sparse checkout copied its configuration
without its patterns, then materialized the entire target tree. Copy active
info/sparse-checkout patterns from the source worktree's private Git directory
during preparation, including when checkout is deferred. Missing patterns are
skipped, empty files are retained, and copy failures roll back registration.
Expose pattern loading and full-index selection through gix_worktree::sparse.
Initial checkout in gix reads the destination's current patterns and marks
excluded target-tree entries with SKIP_WORKTREE and EXTENDED before writing
files and persisting the index. Support cone and non-cone patterns, case
folding, invalid-cone fallback, root entries, and directory pruning. Sparse
index generation and updates to existing checkouts remain outside this API.
Reuse matching decisions for shared directory ancestors with storage bounded
by path depth, and skip index traversal for a validated full-cone selection.
Cover pattern matching with 18 Git-generated baseline scenarios, regression
tests for cache boundaries and ordering, and integration tests for main and
linked sources, deferred checkout, missing or disabled patterns, and rollback.
Add Criterion benchmarks for cone and non-cone selection on synthetic indices
with 20,000 to 200,000 entries, checking membership and flags before timing.
Breaking change: gix_worktree::add::prepare() now accepts the destination
first, followed by an add::Context containing the common Git directory and
an optional source private Git directory, then its existing options. Use
add::Context::new(common_dir) when pattern inheritance is not wanted.
make bounded removal retries configurable
Went through the tests pretty quickly, as is increasingly common.
Expose Options::retry_delay alongside max_retries. The default is 10 ms;
Duration::ZERO retries immediately, and callers can choose a longer delay for
longer (expected) write bursts. Only retryable DirectoryNotEmpty errors with
attempts remaining wait, before restarting traversal. Successful first-pass
removal, zero-retry operation, and terminal failures incur no pause. The default
two retries request at most 20 ms of sleep per root; filesystem operations and
scheduler delays have no wall-clock bound.
Remove the shrinking-entry-count guard. A writer can replace every deleted file
with a new one, leaving the scan count unchanged even though deletion succeeds
for every scanned entry. The old guard then stops before the configured retry
allowance is used. A deterministic regression writes one replacement after each
of the first two scans: the old loop fails on the second pass; the corrected
loop succeeds on the third, even with a zero delay. The retry count bounds
shrinking, equal, and growing workloads without trying to infer writer progress.
Deletion duration or entry counts cannot tell when an independent writer will
finish. Keep the delay an explicit caller policy instead of introducing another
heuristic tied to tree size. No finite retry policy guarantees completion for
arbitrary finite or indefinite writers. Existing porcelain Target::options()
and the re-exported Options expose this setting without another configuration
layer. Downstream exhaustive Options literals must add retry_delay or use
..Default::default().
cap automatic macOS removal at four workers
This is an APFS problem, which is also noticeable when scanning through
metadata, which now caps at 8 at least in dua.
On Linux Ext4 no such limits exist for all I know, so this commit is
a macOS specific fix to ensure decent performance.
Resolve automatic removal concurrency to at most four available logical CPUs
on macOS. None and Some(0) stay automatic; positive explicit limits remain
unchanged, as do defaults on other platforms. Apply the cap in the shared
plumbing options so repository, proxy, and CLI removal inherit it.
Sixteen concurrent unlink workers contend on native APFS. A dedicated comparison
of three and four workers favors four in all 12 matched pairs, including trees
created by Git, gix, and APFS cloning. Median wall seconds (range), four samples
per cell:
| Creator | 3 workers | 4 workers | Less elapsed time |
|---|---|---|---|
| Git | 2.013 (1.878–2.059) | 1.842 (1.820–1.856) | 8.49% |
| gix | 2.873 (2.849–2.890) | 2.597 (2.577–2.673) | 9.59% |
| APFS CoW | 1.577 (1.571–1.594) | 1.429 (1.420–1.432) | 9.42% |
Median per-round 3/4 time ratios are 1.087×, 1.101×, and 1.107× respectively.
One additional single-worker control per creator took 3.258, 3.911, and 2.781 s:
the four-worker medians are 1.77×, 1.51×, and 1.95× faster. Those controls ran
last and are diagnostic, not paired repetitions.
The preceding native worker sweep measured sixteen-worker medians of 5.018 s
for Git-created and 5.819 s for gix-created trees (two samples each). These are
separate measurements, not additional pairs in this comparison. GitButler's
image-derived one-worker override and the old all-core default both give up
native-volume throughput.
2026-10-09, Apple M4 Max, 16 logical CPUs, 64 GiB RAM, macOS 27.0.1 (26A434),
native APFS under /private/tmp; Rust 1.96.1 release probe and Apple Git 2.54.0.
The cached probe uses local Gitoxide 00bb1af, with max-performance, parallel,
both pack-cache variants, SHA-1, and worktree mutation. Explicit removal thread
limits exercise the same deletion path as the new automatic cap. The retry
pause only applies after an error; no concurrent writes were injected here.
Borrow objects read-only from
/Users/byron/dev/git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux, commit
707df3375124b51048233625a7e1c801e8c8a7fd, using independent seed metadata.
The clean seed checks out tree 176a057fce1932fe5057196e63c2a636e1a3cdab:
88,821 tracked files / 1,509,611,994 blob bytes. Native case-insensitive APFS
requires omitting thirteen later case-fold collisions in git ls-tree -r
order: 15,749 bytes, 0.00104% of the source tree.
Each of four rounds creates fresh Git, gix, and CoW destinations with both
removal counts; odd rounds reverse all case ordering. Git checkout uses one
worker, gix its default sixteen. CoW registers with Git without checkout,
uses clonefile() for regular files and index, and recreates symlinks. This is
a deletion fixture, not a timing of GitButler's entire CoW creation workflow.
A small byte/symlink self-check validates the fixture copier.
Synchronize with sync_volume_np(SYNC_VOLUME_WAIT) before creation and removal,
outside timers. Validate clean status before forced removal, excluding status
cost from the removal timer. All 27 samples removed both checkout and private
administration. No build or other benchmark overlapped measurements. One
0.24 s read-side inventory overlapped the second-round CoW/3 case; excluding
that pair leaves medians 1.577 vs 1.430 s, with four winning all remaining pairs.
These are warm-cache timings on one native APFS machine. No new disk-space,
cold-cache, durable-write, or other-platform measurement was made. The old
sparse-image results are unsuitable for choosing native macOS concurrency.
The updated automatic-resolution test failed with 16 instead of 4 before the
change. Removal and bounded late-write regressions pass, including explicit
limits above the cap. Keep results here; discard temporary fixtures and logs.
classify sparse gitlinks as directories on every host
Non-cone directory-only patterns should treat gitlinks as directories on
every host, including when the destination is initially empty. The original
matcher instead hardcoded them as non-directories, reproducing the result
of Git's little-endian ce_to_dtype() bug.
Expose gix_index::entry::Mode::is_dir_for_git_matching() using decoded
modes directly, and document why Git's extra ntohl() conversion is wrong.
Use this classification for sparse matching, so /*/ includes an absent
gitlink and !/module/ excludes it consistently across hosts.
Keep Git-generated baselines while working around its conversion bug:
pre-create the empty gitlink directory only for the reference operation,
allowing Git's filesystem fallback to recover its intended classification.
The gix index-only regression and initial checkout still start without it.
Check included gitlinks as directories rather than reading them as files.
raise MSRV to Rust 1.88
<!-- agent -->
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
gix editor command
<!-- agent -->
Provide a small plumbing command that opens zero or more paths with
Repository::editor()'s Git-compatible selection. Prepare editor definitions with
command-aware argument splitting so PATH-resolved programs run directly while
actual shell syntax still uses the shell, reject explicitly empty settings, and
honor ':' as the no-op editor.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix editor command (d930653)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6428edc)b5b2d54)bc4064c)2125012)f7d4f33)
</details>remove gix tix screen selection Remove the plumbing CLI screen-mode option now that the interactive history always owns the alternate screen. The auto
remove gix tix screen selection Remove the plumbing CLI screen-mode option now that the interactive history always owns the alternate screen. The automatic and half-screen modes depended on inline rendering behavior that is being retired from gix-tix.
Stop accepting --screen for gix tix and its aliases, and remove the mode validation and translation into gix-tix. Construct the reduced gix-tix options directly from the remaining quit and hidden-revision arguments. Keep a command-line regression assertion so the removed option cannot silently return as an ignored argument.
delegate tix commands through gix-tix Embed the complete gix-tix Clap platform in the plumbing command instead of maintaining a second parser and dispatcher. This keeps standalone and plumbing invocations aligned, adds worktree-tip parity, and makes amend and spill available through gix tix without duplicating their execution logic.
show other worktree checkouts in tix Decorate commits checked out by other main or linked worktrees with light-blue name@ labels, replacing the ordinary branch label. Keep the checkout from which tix was opened represented by the graph @ marker and its ordinary local reference, and use directory basenames for other detached worktrees. Keep other-worktree labels visible on the selected row when references are hidden.
Add -w/--worktrees to include every successfully resolved worktree HEAD, including the current checkout, alongside implicit or explicit traversal tips without weakening hidden-revision exclusions. Discover worktrees from their private Git metadata so stale checkout directories remain useful, while malformed, unborn, or inaccessible entries are logged and skipped.
Watch linked HEAD and worktree membership changes so decorations and optional tips stay current, while ignoring unrelated linked indexes, logs, and metadata. Document the behavior and cover current, attached, detached, stale, malformed, hidden-reference, CLI, and watcher cases.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
remove linked worktrees safely
Provide the gix-worktree plumbing needed to recursively remove a linked
checkout and its private Git directory without following symbolic links or
crossing Unix mount boundaries.
Use dua-core for traversal and parallel deletion with progress reporting,
bounded retries for directory-not-empty races, and errors distinguishing
checkout and administration failures. Keep repository validation, dirty-state
checks, lock policy, and branch decisions with higher-level callers.
create linked worktrees
Add transactional linked-worktree administration with rollback, then compose
it in gix with existing reference, checkout, index, progress, and interruption
machinery.
Support attached and detached worktrees from bare or non-bare repositories while
rejecting occupied branches and destinations. Keep move, remove, repair, hooks,
sparse checkout, and relative-link configuration out of scope.
skip symlinked ignore files and protect checkout writes
A tracked .gitignore symlink was absent from the skip-worktree ID
mapping, so ordinary ignore lookup could parse arbitrary external files.
An endless target could also exhaust memory.
Always request no-follow reads for worktree .gitignore files, regardless
of their index entry. Use gix_fs::open_read_only_no_follow() when pattern
loading disallows symlinks, treating skipped links as absent files so
skip-worktree blob fallback remains available. Discard partially read
pattern bytes on failure.
Use the same helper for the worktree .mailmap, reporting symlinks as
errors without reading their targets and identifying worktree read errors
correctly. Explicitly configured pattern files and mailmap.file may
still follow symlinks.
On Windows, inspect nonexclusive checkout handles for symlinks before
truncating with set_len(0) or writing. Retain forced unlink-and-replace
behavior and route symlinks checked out as ordinary files through the
same validated open path. No-follow protection applies to the final path
component on Unix and Windows; leading components can still be symlinks.
Compare ignore lookup and skip-worktree fallback against isolated Git
check-ignore calls. Cover mailmap policies and checkout collisions with
file, directory, and dangling symlink targets, including links created
after the Windows path check and validation before truncation.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
10c58bb)87433ed)f962ed1)575113d)gix-testtools (ce9e6bd)278d7ec)0ec3bb7)sha1 and sha256 forwardings for all crates (09b982c)1cd36be)GIX_TEST_FIXTURE_HASH for gix-traverse-tests (9f064a3)ab2fee1)2cb17b2)e10d5f6)3675a8d)adb8328)
</details>support cloning a single revision <!-- agent --> A full object ID passed through with_ref_name() produced an object-ID refspec mapping and panicked wh
support cloning a single revision <!-- agent --> A full object ID passed through with_ref_name() produced an object-ID refspec mapping and panicked while clone assumed every mapping had a name. Branch and tag checkout also retained ordinary clone tracking semantics instead of offering a single-revision mode.
Add PrepareFetch::with_revision() and gix clone --revision for full refs, HEAD, and full object IDs. Revision clones use a one source-only implicit refspec, detach HEAD to the fetched commit, create no ordinary refs, persist no fetch refspec, and disable tag following. Existing with_ref_name() and --ref behavior stays unchanged.
This follows Git commit 337855629f59 (builtin/clone: teach git-clone(1) the --revision= option) and its t/t5621-clone-revision.sh behavior.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix-date (613ff86)keep descendants of ignored directories excluded
I looked at this carefully, and ended up having a better comment
to provide an example for what this covers.
Ultimately, this is test extension is still minimal compared to the
behaviour that it enables, scoped status, but I think it's fine
in there interest of less code.
Scoped status walks can enter an ignored directory when a pathspec
matches. If a deeper directory matches a negated rule such as !out/,
the ignore stack previously stopped at that nearer match and exposed its
contents as untracked. Tix uses scoped walks for filesystem refreshes,
so ignored Cargo output appeared after unrelated worktree events and
disappeared after a full refresh.
Continue through negated directory matches to check excluded ancestors.
Keep the nearest negation as the fallback when no ancestor excludes the
path, and preserve the precedence of positive directory matches,
including precious-file handling.
Extend the Git-reference fixture below a negated child directory and
refresh both hash archives. The extended fixture fails with the previous
matcher. All directory-walk, status, and worktree tests pass, as do the
SHA-256 ignore baseline, formatting, and Clippy with -D warnings.
Clippy retains the workspace's existing removed-lint warning.
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
53f880c)gix-object (91bfab0)4d5ba23)
</details>add configurable terminal screen modes.
add configurable terminal screen modes.
hide revision ancestry in tix
add tix to the gix CLI
add explicit gix config show subcommand.
add gix config list for showing the git-configuration files.
add the gix config fmt subcommand
Expose the gix-config whitespace formatter as
gix config fmt [--in-place] [in-file] [out-file]: with no in-file it
formats the repository-local configuration, and with no out-file it writes
to stdout. The repository is only opened when the repository-local
configuration is needed, so formatting an explicit file works outside a
repository too.
add gix status --untracked flag
This allows to control how untracked files are folded, but also
can completely turn dirwalking off.
add gix free remote refs to list and write remote refs.
Add gix free remote refs to perform an upload-pack handshake, discover
the remote reference advertisement, and print the refs without negotiating
or receiving a pack.
The command can also write the advertised refs into a standalone ref store:
gix free remote refs --refs-directory out-refs <url>
preserve multiple remote URLs
Configured remotes can have multiple remote.<name>.url or remote.<name>.pushUrl
values, but gix::Remote kept only one value because lookup used the singular
config accessor. That meant the most recent config value won, while Git exposes
every effective URL and uses the first one for the singular get-url form.
Add ordered URL storage to gix::Remote and expose Remote::urls(Direction) for
all effective URLs. Keep Remote::url(Direction) as the singular compatibility
API, now returning the first effective URL. Fetch URLs used as push fallbacks
try pushInsteadOf first and then insteadOf, matching Git behavior.
The regression fixture records Git 2.50.1 behavior with git remote get-url: without --all it prints the first configured URL, and with --all it prints all configured URLs in order for both fetch and push.
make exclude queries index-aware <!-- agent -->
gix exclude query reported ignore matches for tracked files and directories
containing tracked entries, unlike git check-ignore. Positional arguments were
also interpreted as pathspecs while stdin supplied paths.
Treat positional and stdin input uniformly as paths, normalize them relative to the repository, and suppress ignore matches for indexed files or directories containing indexed entries. This changes positional arguments from pathspecs to paths.
Add journey coverage for tracked and untracked paths below ignored directories, stdin from a nested working directory, ignore-pattern display, and positional output order.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix config list for showing the git-configuration files. (bd595de)gix config fmt subcommand (87a5e89)gix-attributes (e11d7a2)gix-config (376e946)gix status --untracked flag (9316ff8)gix free remote refs to list and write remote refs. (6767b30)
</details>gix-testtools (0cbe539)Store::at() where possible (17fea2a)GIX_TEST_FIXTURE_HASH for more tests (bbea2c4)with-hidden()
This is achieved by precomputing a hidden-frontier which the actual
traversal then cannot cross.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f9fbcba)7d50c30)gix-object (6df1d55)6f47e98)with-hidden() (f6d993e)2a5db88)e4f380e)444a92b)3e05ca3)package.include patterns more specific so they don't match ignored files (c2c917f)98bae84)
</details>Strange - automatic release notes weren't generated or didn't arrive here. Have to look into that. Meantime, let's use the GitHub generated notes.
Strange - automatic release notes weren't generated or didn't arrive here. Have to look into that. Meantime, let's use the GitHub generated notes.
fuzzed_timeout on windows-11-arm by @EliahKagan in https://github.com/GitoxideLabs/gitoxide/pull/2619gix-pack by @cruessler in https://github.com/GitoxideLabs/gitoxide/pull/2602GIX_TEST_FIXTURE_HASH for gix-index tests by @cruessler in https://github.com/GitoxideLabs/gitoxide/pull/2598should_interrupt per entry in index_as_worktree by @sharifhsn in https://github.com/GitoxideLabs/gitoxide/pull/2631Full Changelog: https://github.com/GitoxideLabs/gitoxide/compare/v0.54.0...v0.55.0
sha1 and sha256 features to gix.
This way one can control which hashes are compiled in exactly,
while having reasonable defaults automatically.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
c389a2c)6183fd0)6bdb331)e8bf096)sha1 and sha256 features to gix. (3832916)gix-hash (e71c703)f7277f3)
</details>gix dirwalk as a way to run gix-dir directly This is mostly for testing walks specifically, without needing them as part of gix clean or gix status.
gix dirwalk as a way to run gix-dir directly
This is mostly for testing walks specifically, without needing them as part
of gix clean or gix status.gix merge tree --message '' to allow creating commits
This is useful for controlling cherry-picks precisely.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix dirwalk as a way to run gix-dir directly (add4cf4)gix merge tree --message '' to allow creating commits (6ab327e)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ecf90fc)9327b73)
</details>This release was made to supersede the borked gix v0.82 release, as it released gix-actor as patch-update which broke v0.81 and probably earlier versi
This release was made to supersede the borked gix v0.82 release, as it released gix-actor as patch-update which broke v0.81 and probably earlier versions as well.
<csr-id-4ad0dbf8a5274d591f56e4af8ad745f3567f9543/> use graph painting for hide() to ensure correct behavior The hide() function now fully traverses all hidden tips and marks all reachable commits as Hidden before returning. This "graph painting" approach ensures correct behavior regardless of graph topology or traversal order, matching git's behavior.
Previously, hidden commits were traversed lazily during iteration, interleaved with interesting commits. While this worked in most cases, the new approach is simpler and more robust.
Added tests to verify correct behavior when:
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
d66ac10)8c88c59)647d008)d568b3d)gix-traverse (209641b)4ad0dbf)8bceefb)7ce3c55)f7d0975)
</details>Use std::ControlFlow where possible
std::ops::ControlFlow where possible<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cbbdef5)562e684)fa302a1)std::ops::ControlFlow where possible (5c1bd03)0a333e5)c663b3f)
</details>4 commits contributed to the release over the course of 5 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
7be8f90)d914d95)4edc5dd)211b4fb)
</details>Progress report January 26 by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2393
gix-error conversions: gix-actor by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2396tracing instead of tracing-core to re-use the standard macros. by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2401core.bare being known or not by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2403blocking-http-transport-reqwest doesn't enable reqwest's default features by @fenhl in https://github.com/GitoxideLabs/gitoxide/pull/2404bytes to a fixed version by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2411gix-error by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2400imara-diff 0.2 in gix-blame by @cruessler in https://github.com/GitoxideLabs/gitoxide/pull/2420status work despite broken or invalid symlinks. by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2440Full Changelog: https://github.com/GitoxideLabs/gitoxide/compare/v0.50.0...v0.51.0
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
115e208)d6c5b9d)
</details>4 commits contributed to the release over the course of 12 calendar days.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
Exn::into_box() to Exn::into_inner(). (939b8fc)exn to most pressing needs of gitoxide (abedade)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
21fecdf)93dd630)703644c)
</details>2 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
82ff92f)3313233)
</details>14 commits contributed to the release over the course of 99 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
89fb308)4da2927)6cc8464)9365cc3)838ff95)dc7343c)79ba9d0)651f9fa)4289ae6)202bc6d)d64f257)589d63e)007e3f6)784c046)
</details>allow credential fill with gix credential fill to run without a repo
gix credential fill to run without a repoRemove doc_auto_cfg feature to fix docs.rs documentation.
It is part of doc_cfg feature since https://github.com/rust-lang/rust/pull/138907
This fixes the docs.rs build
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix credential fill to run without a repo (924cd62)doc_auto_cfg feature to fix docs.rs documentation. (6f469a6)
</details><csr-id-6f469a6fea59c88e6c69a5f94b0bc8a5977cb75b/>
gix credential fill to run without a repo<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
commit::Simple::hide() to hide a given set of tips.
That means, these tips and all their ancestors will be hidden from
the traversal.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5a919c4)65037b5)dab97f7)a9a8ea1)92febae)219655f)commit::Simple::hide() to hide a given set of tips. (1b08fd9)c3f06ae)
</details>Add commit::Either::commit_time()
commit::Either::commit_time()<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
d2b4c44)gix-index (bfc4880)800738a)4408166)8be3193)9c3e288)commit::Either::commit_time() (b40ba17)8d4c4d1)
</details>3 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e104545)5f7f805)631f07a)
</details>add a gix commit sign prototype
gix commit sign prototypegix branch list<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix commit sign prototype (aacc326)gix branch list (58b5060)gix tag list when JSON is requested (fb2766b)
</details>gix commit sign prototypegix branch list<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
8699d0f)82f788e)gix commit sign prototype (aacc326)4da2927)6cc8464)gix-blame (a721e74)gix-blame (268dac4)525873f)04650a7)6651548)e537611)gix branch list (58b5060)c149116)gix tag list when JSON is requested (fb2766b)
</details>gix_date::Time on demand.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cc5b696)db0b095)0bf84db)3b1bef7)c3c6504)b07f907)b5e9059)68e6b2e)420e730)
</details>add first debug version of gix tag list
add first debug version of gix tag list
gix revision list --long-hashes for faster iteration.
The performance of the short-hash generation was improved as well.
support for commitgraph list from..to to exercise the new 'hide' capability.
Enable precious file parsing in gix CLI by default, allow overrides.
That's pretty neat as one can now set GIX_PARSE_PRECIOUS=0 in the environment
to disable precious file parsing, good to see what difference it makes.
It's also possible to do this wiht gix -c gitoxide.parsePrecious=0.
add support for multiple blame ranges like gix blame -L <range> -L <other-range> ...
Update the blame subcommand to handle multiple line ranges. This allows specifying multiple -L options similar to the usage of git.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix tag list (37d3bf2)gix revision list --long-hashes for faster iteration. (ab52a49)gix-blame (4afc51d)commitgraph list from..to to exercise the new 'hide' capability. (c5bc49f)gix CLI by default, allow overrides. (1df1ebb)gix blame -L <range> -L <other-range> ... (36a6ffe)gix-blame (8143d69)
</details>commit::Either::tree_id()commit::find and commit::Either
For a way to obtain a commit either by ODB lookup, or by retrieving
it from the commit-graph.
This is useful for the implementation of custom traversals.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 2 times to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b41312b)38dff41)544cdaf)commit::Either::tree_id() (625f9dd)85b060c)3c1b1df)8776a3e)9dcfd15)16a248b)8e96ed3)aa05ef0)commit::find and commit::Either (47c8a1f)8df0db2)
</details>This is a bit empty as release notes got lost in a series of accidents, but it looks like it wouldn't have been too informative anyway.
This is a bit empty as release notes got lost in a series of accidents, but it looks like it wouldn't have been too informative anyway.
<csr-id-17835bccb066bbc47cc137e8ec5d9fe7d5665af0/>
<csr-id-22f8939d862c74f2f55c74fded2f066a6d6536a1/> tree::depthfirst() traversal
A depth-first traversal yields the .git/index order.
It's a breaking change as the Visitor trait gets another way
to pop a tracked path, suitable for the stack used for depth first.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
dea106a)1f6390c)7ec21bb)rust-version to 1.70 (17835bc)0ab4f64)tree::depthfirst() traversal (22f8939)d22937f)
</details>add topo::Builder::new fn for creating a bare builder Previously, the only way to create a Builder would be via Builder::from_iters. That fn takes as
<csr-id-59148a2043f0f502edfb895e19843b7fab6efeac/> add topo::Builder::new fn for creating a bare builder
Previously, the only way to create a Builder would be via
Builder::from_iters. That fn takes as arguments both the tips and
ends, and used to be the only possibility for specifying either of them
during the building process. However, in order to enhance the builder-
likeness of Builder, we recently introduced fns with_tips and
with_ends for adding additional tips and ends.
With those fns, the only component which needs to be supplied up-front
is find. Users can specify and empty Iterator and None for tips
and ends respectively when calling Builder::from_iters and add
additional tips and ends at their leisure, without the need to chain
Iterators or collecting them in some external data structure.
Now, calling Builder::from_iters with a empty lists for tips and ends
is a bit awkward. Thus, we provide a new method for creating a bare
Builder.
<csr-id-a7a8d7cd79550033cc9e0277a0ab9155e5ab6739/> add topo::Builder::with_tips fn for adding tips after from_iters
Currently, Builder::from_iters takes as arguments both the tips and
ends. Previously, this would be the only possibility for specifying
either of them during the building process. To enhance the
builder-likeness of Builder, we recently introduced a fn for adding
additional ends.
This change introduces a fn which allows adding additional tips after
initial construction of a "fresh" Builder, allowing for more usage
patterns.
<csr-id-1c1d03775ce169dc3a353c2b81ce5770cbda15f5/> add topo::Builder::with_ends for adding ends after from_iters
Currently, Builder::from_iters takes as arguments both the tips and
ends, and it's the only possibility for specifying either of them during
the building process. Considering that ends in Builder::from_iters
is an Option, this is not very builder-like and obstructs some
use-cases.
This change introduces a fn which allows adding additional ends after
initial construction of a "fresh" Builder.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
c1ba571)7ea8582)3e63721)topo::Builder::with_tips and with_ends for non-default pred (d9426f4)67f20b1)55eaf52)29e3bbf)topo::Builder::new fn for creating a bare builder (59148a2)topo::Builder::with_tips fn for adding tips after from_iters (a7a8d7c)topo::Builder::with_ends for adding ends after from_iters (1c1d037)e8b3b41)
</details>Add missing command docs + small style fixups Changes that affect the help/usage text shown at runtime:
<csr-id-f952c101cc8686e685074e8604e0f332c06d6767/> Add missing command docs + small style fixups Changes that affect the help/usage text shown at runtime:
Add descriptions for a few gix commands that didn't have it:
gix is-clean, gix is-changed, and gix env.
Add a description of the debug-only ein panic command.
Small spacing and capitalization improvements for consistency.
Add a line break in a /// block for brevity of the top line.
Changes to code style that do not affect what is shown at runtime:
Add . at the end of some /// first lines. (This doesn't
affect runtime behavior because clap normalizes this away.)
Put /// above all #[...] in a few places where it wasn't.
Adjust comment wrapping in a couple of places for clarity.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-f952c101cc8686e685074e8604e0f332c06d6767/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4000197)8ce4912)bc9d994)7a40648)0f0e4fe)db5c9cf)
</details>add first 'debug' version of gix diff file
gix diff fileClippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix diff file (dbb1532)gix-blame (8a31d88)--since (330711d)gix-blame (e7084d8)<csr-id-64ff0a77062d35add1a2dd422bb61075647d1a36/>
<csr-id-1dbb94adeeea4ca09a7899697a3380c1e6a03130/> add option to traverse commits from oldest to newest This change introduces an enum to control commit traversal order. Users can now choose between newest-first or oldest-first traversal. The default behavior remains newest-first, but it can be toggled by passing a CommitTimeOrder to a Sorting::ByCommitTime* variant.
This feature is particularly useful for searching early repository history. The implementation remains largely agnostic to this change, with only minor logic adjustments in key areas as necessary.
The reversed order is achieved by inverting the PriorityQueue key when an oldest-first traversal is requested.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
3f7e8ee)795962b)64ff0a7)20f9b3f)6ac14d7)1dbb94a)649f588)beba720)37ba461)2e0ce50)f992fb7)ec69c88)e82f795)5ef8ae8)
</details>add gix env to print paths relevant to the Git installation.
gix blame -L start,endgix env to print paths relevant to the Git installation.gix blame to the CLI
That way it's possible to see the blame result of any file in the
repository.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix blame -L start,end (4a78395). for consistency (ddddf02)gix env to print paths relevant to the Git installation. (75d689f)gix blame to the CLI (80e5804)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b3ff033)209b6de)
</details>add first 'debug' version of gix log It's primarily meant to better understand gix blame.
gix log
It's primarily meant to better understand gix blame.--tree-favor to gix merge tree|commit.
With it one can decide which side to favor in case of
irreconcilable tree-conflicts.gix merge file now uses THEIRS instead of OURS where needed<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix merge file now uses THEIRS instead of OURS where needed (0727b56)gix log (c7e04e9)gix-diff (960773e)--tree-favor to gix merge tree|commit. (471e046)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f2b522d)a65a17f)d19af16)0f25841)5871fb1)9fd1090)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6232824)a1b73a6)0470df3)99c00cc)bf3d82a)c1d7c02)1dfa90d)tar files (dcab79a)9fa1054)9c65d98)ea12fc2)68cbea8)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4f98e94)9511416)d3588ca)
</details>3 commits contributed to the release over the course of 14 calendar days.
gix merge commit --debug
This yields additional debugging information with details about detected conflicts.gix merge commitsgix merge tree to merge trees similarly to git merge-tree.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix merge commit --debug (0a5993f)gix merge commits (4a5afc7)gix (8d590f3)gix merge tree to merge trees similarly to git merge-tree. (84707c2)add Url::path_query_fragment()
Expose the decoded path, query pairs, and fragment of Git remote URLs
separately. Consumers can identify repository paths and inspect HTTP(S)
parameters without implementing scheme-specific splitting and decoding.
Recognize delimiters before decoding and reuse validated original spelling
to borrow decoded bytes. Preserve encoded separators, nested escapes,
ordered duplicate query keys, and literal percent text after construction
or mutation. Query pairs use form decoding (+ becomes space); SSH/SCP
paths, existing accessors, and serialization keep their behavior.
Reference Git's connect.c::parse_connect_url() and url.c at
1630431f326e. Use fetch-pack --diag-url to check SSH delimiters;
standalone url-parse does not model that transport.
migrate errors to gix-error
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
Url::path_query_fragment() (cd90fe1)topo more similar to Ancestors, but also rename Ancestors to Simplecommit::ancestors to be more consistent with other plumbing crates.
This makes sure that each time is reached by only a single path.State as ultimately,this capability
wasn't all that useful.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
1f6c8ab)095c673)5755271)u8 for WalkFlags in the hopes that this can save memory. (a5751bc)55f379b)f72ecce)b590a9d)topo more similar to Ancestors, but also rename Ancestors to Simple (2a9c178)commit::ancestors to be more consistent with other plumbing crates. (3f938fa)ee13bdb)e0969c3)25b3d23)5b3dfbb)ecc049c)
</details>support for listing worktrees with gix worktree list
support for listing worktrees with gix worktree list
add first 'debug' version of gix diff tree.
It's primarily meant to better understand gix blame.
add new gix cat command.
It only prints things without fuzz.
Inspired by https://youtu.be/JYH5ILv5g1g?si=bHLBPFJiZyRUTl6u&t=211.
add gix merge-file with similar features as git merge-file
gix merge-base for the CLI
For now it only supports the standard merge-base, but more derivatives
can be added easily on demand.
gix clean warning and help for worktree fixgit clean options
-r/--repositories and --skip-hidden-repositories to make it
clearer what their relationship is, avoid creating the false
impression that repositories are never deleted in the absence of
-r/--repositories, and note that --skip-hidden-repositories
is sometimes needed to preserve not only separate repositories but
the (probably rarer) case of hidden nested worktrees of the current
repository.time to jiff
This swaps out time for jiff. It doesn't completely remove time
from the dependency tree. The last remaining use of time is in
prodash, outside of the gitoxide project.<csr-id-786bfec7c2cf25a68705b6ef09ba6390600742b8/> Unify style in config support info
This builds on b31d6b7 (#1531) by adjusting the capitalization and
quoting style of string arguments in progress.rs that help
document the status of what configuration options are and are not
planned.
Since I believe these strings are not usually rendered as Markdown, and most places that code formatting in Markdown would be used were already written with single quotes, this applies that quoting style consistently.
This applies initial capitalization, which was sometimes but not
always done. It does not apply a consistent style for when a
string will end in a ., which seems already to differ
deliberately for reasons of clarity. That can be adjusted later.
A small amount of minor rewording for clarity is also included.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix commit-graph is (49bca2a)gix diff tree. (0c554e0)gix cat command. (9c8bc03)gix merge-file with similar features as git merge-file (3da2da9)gix merge-base for the CLI (7249291)time to jiff (28ac657)gix clean warning and help for worktree fix (6eb4ea6)gix worktree list (c7213bc)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b050327)52c3bbd)3e5c974)f8ce3d0)
</details>resolve Windows directory symlink chains
resolve Windows directory symlink chains
Delaying symlinks until regular files are written is insufficient on
Windows: an early link can target another link that has not been created
yet. A single target probe then leaves a file link where a directory link
is required, making paths such as a-child -> z-dir/nested unusable.
Git for Windows retries unresolved links when directory links appear.
Add gix_fs::symlink::create_or_delay() and retry unresolved checkout
entries while other links make progress. When a pass makes no progress,
create the remaining dangling or cyclic links with the existing file
fallback.
Completed links need no removal or recreation. For forced overwrites,
try creation before unlinking so a deferred replacement leaves the
existing link intact if a later object error aborts checkout.
cap automatic macOS checkout at four workers
Using all logical cores for checkout causes APFS creation contention on
macOS. Benchmark fresh checkouts of the Linux tree to choose a default
that preserves throughput without starting unnecessary workers.
Resolve None and Some(0) to at most four available logical cores in
shared checkout plumbing, so clone, linked-worktree creation, and index
checkout inherit the cap. Positive explicit limits remain overrides;
other platforms retain their existing defaults, and builds without
gix-parallel/parallel continue to run on the calling thread. Update the
checkout.workers and clone documentation accordingly.
On an Apple M4 Max with 16 logical CPUs and native case-insensitive APFS,
the initial worker sweep measured median checkout times of 2.564 s at
four workers, 3.774 s at eight, and 6.874 s at automatic sixteen. An initial
probe using newer offline-resolved dependencies favored five workers,
but that advantage did not reproduce with the workspace's locked versions.
The final comparison using those locked versions covers every execution
order of four, five, and six workers, with six samples per setting:
| Workers | Median seconds | Range |
|---|---|---|
| 4 | 2.664813 | 2.533386–3.106756 |
| 5 | 2.665293 | 2.513454–2.938505 |
| 6 | 2.903967 | 2.843629–4.047406 |
Four and five split the paired wins three to three and have effectively
identical medians. Choose four to obtain the same measured throughput
with one fewer worker, matching the existing macOS removal cap.
A separate three-round comparison with the workspace's locked dependencies
checks the same collision-safe Linux tree against Apple Git 2.54.0. Rotate
execution order so each method runs first, second, and third once:
| Checkout | Median seconds | Range |
|---|---|---|
| Git, one worker | 7.293862 | 7.279254–7.394098 |
gix, one thread |
6.875375 | 6.822443–6.958276 |
gix, four workers |
2.376388 | 2.349792–2.493034 |
Git runs checkout-index --all --prefix=<fresh-destination>/ with
checkout.workers=1 against the prebuilt retained index. Its timer includes
process startup and index loading; gix times the checkout call with an
already loaded index. Index preparation, volume synchronization, complete
Git content/mode/symlink validation, and cleanup are outside both timers.
These are initial-checkout references, not timings of full clone or branch
switch workflows. No builds or tests overlap the timed samples.
Raw wall seconds in execution order:
gix/1 6.822443, gix/4 2.376388.gix/4 2.493034, Git 7.279254, gix/1 6.958276.gix/1 6.875375, gix/4 2.349792, Git 7.293862.All nine checkouts pass Git content verification. This is a separate run
from the four/five/six comparison above; compare methods within each run.
A separate four-pair run compares Apple Git 2.54.0 with
checkout.workers=3 and checkout.workers=4 on the same retained tree,
using checkout-index --all --prefix=<fresh-destination>/ as above.
Alternate execution order between rounds:
| Git workers | Median seconds | Range |
|---|---|---|
| 3 | 4.261867 | 4.058227–4.361033 |
| 4 | 3.745698 | 3.611599–3.768478 |
Four workers win all four pairs; three offers no advantage here. A
separate warmup with GIT_TRACE2_EVENT confirms four checkout--worker
processes; exclude that traced 3.367775 s sample from the timing table.
All eight untraced checkouts pass Git content, mode, and symlink checks.
Volume synchronization, validation, and removal remain outside timers;
no probe compilation overlaps these measurements.
Raw wall seconds in execution order:
This later run measures Git's worker scaling. The earlier one-worker Git
and gix figures are reference timings from their own run, rather than
additional matched samples in this comparison.
Borrow objects read-only from the bare Linux repository at
/Users/byron/dev/git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux,
commit 707df3375124b51048233625a7e1c801e8c8a7fd. Use independent metadata
and fresh destinations under /private/tmp, omitting thirteen later
case-fold collisions that native APFS cannot represent. The retained tree
contains 88,821 entries, including 79 symlinks, and 1,509,611,994 blob bytes.
Time only checkout; synchronize the volume, verify content, executable
modes, and symlinks against isolated Git, and remove destinations outside
the timer. No builds or tests overlap timed samples. Keep the benchmark
method and decisive measurements in this commit message.
These warm-cache initial-checkout results cover one Mac and one volume.
They do not establish an optimum for every filesystem, repository, filter
pipeline, or incremental checkout. Explicit worker limits remain available
for those workloads; no cold-cache or durable-write benchmark was made.
mailmap check similar to git check-mailmap.
That way it becomes a little easier to maybe try out other special cases
in the wild.gix clone with --ref support.
--ref is similar to --branch, but was renamed as it also supports
tags for example.<csr-id-202f3e48a96b38d32b11d28449358c7d1f3546ff/> Make it easier to compile gitoxide as dynlib
And also optimize compilation time: By making plumbing and porcelain
as modules the lib.rs, they can be compiled after the rmeta for the
dependencies are generated.
For the uni.rs which uses both plumbing and porcelain, this would avoid
compiling these two modules twice.
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
mailmap check (3e08fa3)mailmap check similar to git check-mailmap. (2a56387)gix clone with --ref support. (9bf01e4)src/plumbing/main.rs (4596a39)preserve allocation failure sources
rubberstamp
Keep the original TryReserveError inside the OutOfMemory I/O error so structured classification can distinguish allocator failure without treating malformed stream metadata as corruption.
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
eb6aa8f)6a2e0be)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
3 commits contributed to the release over the course of 1 calendar day.
<csr-id-3bd09ef120945a9669321ea856db4079a5dab930/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
972241f)8c492d7)rust-version manifest field back to 1.65. (3bd09ef)
</details>This release contains fixes relevant to the safety of checkouts:
This release contains fixes relevant to the safety of checkouts:
checkout respects options for core.protectHFS and core.protectNTFS.
This also adds gitoxide.core.protectWindows as a way to enforce
additional restrictions that are usually only available on Windows.
Note that core.protectNFS is always enabled by default, just like
it is in Git.
more robustness in the face of a trampling-herd of threads loading a single index. The motivating example is here: https://github.com/praetorian-inc/noseyparker/issues/179
Previously, it was possible for a trampling herd of threads to consolidate the disk state. Most of them would be 'needs-init' threads which could notice that the initialization already happened, and just use that.
But a thread might be late for the party and somehow manages to not get any newly loaded index, and thus tries to consolidate with what's on disk again. Then it would again determine no change, and return nothing, causing the caller to abort and not find objects it should find because it wouldn't see the index that it should have seen.
The reason the thread got into this mess is that the 'is-load-ongoing' flagging was racy itself, so it would not wait for ongoing loads and just conclude nothing happened. An extra delay (by yielding) now assures it either seees the loading state and waits for it, sees the newly loaded indices.
Note that this issue can be reproduced with:
'./target/release/gix -r repo-with-one-pack -t10 --trace odb stats --extra-header-lookup'
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
core.protectHFS and core.protectNTFS. (886d6b5)Store::at() where possible (17fea2a)replace fs with gix-fs
gix-fs already provides the filesystem helpers and recursive walkers.
Keeping their duplicate implementation in gix-features adds unnecessary
filesystem dependencies to the foundational feature crate.
Remove the fs module and the walkdir and fs-read-dir features. Migrate
workspace callers to gix_fs, move traversal requests to gix-fs/walkdir,
and update the manifests, lockfile, traversal documentation, and feature
check script together.
fs with gix-fs (cf1ba49)<csr-id-aea89c3ad52f1a800abb620e9a4701bdf904ff7d/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e1aae19)e78a92b)4454c9d)aea89c3)1691ba6)7549559)35439de)
</details>add gix status --ignored support
add gix status --ignored support
add gix status --index-worktree-renames
This enables rename-tracking between worktree and index, something
that Git also doesn't do or doesn't do by default.
It is, however, available in git2.
gix status with submodule and rewrite support.
Submodule changes are now picked up as long as the submodule is
in the index.
Further, it's possible to enable rename-tracking between
index and worktree separately.
add gix is-clean|is-changed
It's a good way to compare the time it takes to run a full status
compared to a quick is-dirty check.
gix submodules list --dirty-suffix for dirty-information
This is a submodule-centric and greatly simplified way of obtaining
describe information with dirty-suffix.
Note that status information is also possible, but it seems
hard to display nicely, which this command isn't great at
in the first place.
add gix commit describe --dirty-suffix
That way a suffix will be added depending on the dirty-state of the repository.
gix status --format to communicate the current format is very simple. (23bea36)gix status --ignored support (84c74ff)gix status --index-worktree-renames (66e87cd)gix status with submodule and rewrite support. (61c002b)gix is-clean|is-changed (98b3680)gix submodules list --dirty-suffix for dirty-information (afd20ca)gix commit describe --dirty-suffix (58231b4)migrate errors to gix-error
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
gix-object::Find trait<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
55d386a)d3dcbe5)ff99a18)gix-object (203d69c)c8bd660)gix-object::Find trait (806ea47)gix_object and gix_odb. (24e319e)c0e72fb)b65a80b)
</details>add gix clean --patterns-for-entries|-m to help with wildcards.
gix clean --patterns-for-entries|-m to help with wildcards.gix clean<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
-n argument as no-op to make them more compatible. (8959b21)gix clean --patterns-for-entries|-m to help with wildcards. (9863d75)gix clean (e8597f3)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
68e5432)1347a54)995bc84)
</details>Add rev parse --reference. It's similar to git rev-parse --symbolic-full-name.
rev parse --reference.
It's similar to git rev-parse --symbolic-full-name.mark gix::interrupt::init_handler() as unsafe
The passed interrupt() argument will be called from a signal
handler, so that needs to be documented and the call sites need to
state that they fulfill the contract.
Thanks to @Manishearth for pointing this out.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
rev parse --reference. (193ffcd)gix::interrupt::init_handler() as unsafe (59b8104)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
7891fb1)8a60d5b)
</details>gix rev parse --format to provide different versions of the same content. This only applies to blobs, but allows to obtain different versions of the s
gix rev parse --format to provide different versions of the same content.
This only applies to blobs, but allows to obtain different versions of the same blob
like:
--trace mode, greatly increase message-buffer size.
That way, it's much less likely that messages will get lost
due to being overwritten before they can be displayed every
100ms or so.GITOXIDE_* environment variables to GIX_#<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
GITOXIDE_* environment variables to GIX_# (2189cee)gix rev parse --format to provide different versions of the same content. (cf51a4d)gix-diff (1706e23)diff::resource_cache() low-level utility for rapid in-memory diffing of combinations of resources. (4aea9b0)fsck connectivity into just fsck much like git fsck (7ab5c76)--tree-style raw. (8dfbb4b)-c options are given on the command-line. (f9ae1bc)--trace mode, greatly increase message-buffer size. (b230078)gix free discover to inform about repository discovery. (886289f)dyn trait where possible.
This reduces compile time due to avoiding duplication.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
8bd0456)375db06)dynification (f658fcc)dyn trait where possible. (072ee32)363ee77)
</details>This release includes an overhaul of the url parsing implementation, allowing more urls to be parsed correctly and refining the error messages for inv
This release includes an overhaul of the url parsing implementation, allowing more urls to be parsed correctly and refining the error messages for
invalid ones. Improvements include the added support for ssh aliases (github:byron/gitoxide has previously been parsed as local path), adjustments
around the interpretation of colons in file names (previously we disallowed colons that were not followed up with a slash character) and some smaller
changes that bring the interpretation of file urls more in line with Git's implementation.
There are still many (edge) cases in Git's url parsing implementation which are not handled correctly by Gitoxide. If you notice any such deviation please open a new issue to help us making Gitoxide even more correct.
gix status auto-writes changed indices.
This prevents expensive operations to re-occour.gix status -s/--statistics to obtain additional information on what happened.
This is useful for understanding performance characteristics in detail.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix status auto-writes changed indices. (46e5919)gix status -s/--statistics to obtain additional information on what happened. (7ba2fa1)
</details><csr-id-229bd4899213f749a7cc124aa2b82a1368fba40f/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
30b2761)f23ea88)8f3f358)73c685a)229bd48)4604f83)6b4a303)ef8ccd9)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
16295b5)c4cc5f2)5cb3589)2fc66b5)9064ea3)
</details>This release contains a security fix which assure URLs like 'ssh://-oProxyCommand=open$IFS-aCalculator/foo' will not execute attacker-controlled strin…
This release contains a security fix which assure URLs like 'ssh://-oProxyCommand=open$IFS-aCalculator/foo' will not execute attacker-controlled
strings. The above can, on MacOS, launch the calculator app when using it with gix clone for example, up to v0.29.0.
gix status with basic index-worktree comparisongix free index from-list and gix index from-tree gain --skip-hash.
This flag can be derived from options, but thus far we have no higher-level
writing of the index so this has to do to see the difference in performance.ein and gix now share some code via the gitoxide library.
This can slightly improve compile times as well, even though it wasn't measured.prodash
It makes proper usage of Progress types easier and allows them to be used
as dyn traits as well.dyn trait where possible.
This reduces compile time due to avoiding duplication.Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ein and gix now share some code via the gitoxide library. (d3ac691)gix status with basic index-worktree comparison (f094f71)dynification (f658fcc)dyn trait where possible. (072ee32)prodash (ed327f6)gix-index and pass skip-hash through for performance.. (713cd59)gix free index from-list and gix index from-tree gain --skip-hash. (3ff5ac0)index.skipHash (773b6e3)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4aca8c2)68ae3ff)c70e54f)e4dded0)
</details>gix submodule subcommand for simple submodule listing and information retrieval
gix submodule subcommand for simple submodule listing and information retrievalgix index entries --recurse-subomdules to also list submodules.gix index entries with styles and pathspecs.
This adds support for more simple git style, which is faster and thus
allows for more direct comparisons to git ls-files.gix commit verify-signature to do something akin to git ... --show-signature.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix submodule subcommand for simple submodule listing and information retrieval (1ccbe16)gix index entries --recurse-subomdules to also list submodules. (6bc69e3)gix (ca972a2)Defaults::from_environment() when parsing pathspecs. (2a99034)gix index entries (22477bd)gix index entries with styles and pathspecs. (c30ac0c)gix (a201f0d)gix commit verify-signature to do something akin to git ... --show-signature. (cd6cfe4)gix-archive (feba76d).gitmodule file abstraction (6a2e6a4)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
27e8c18)00f96fb)b407461)gix-date (fba45c6)9cfc4aa)
</details>8 commits contributed to the release over the course of 29 calendar days.
gix archive<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix archive, which is where it should shine. (567b1a4)gix archive (32bbb8b)commit::Sorting::ByCommitTimeNewestFirstCutoffOlderThan {time_in_seconds_since_epoch} to seconds.
This is possible now that there is a type for the time with that name.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ea9f942)18b0a37)just fmt (871dd0b)aa16c8c)4f635fc)8d2e6a9)commit::Sorting::ByCommitTimeNewestFirstCutoffOlderThan {time_in_seconds_since_epoch} to seconds. (e4e8ddc)gix-actor (4a80e86)gix-date (d575336)
</details>This release fixes a possibility for V1 fetches to deadlock if negotiation would span multiple rounds (see issue #882) for details.
This release fixes a possibility for V1 fetches to deadlock if negotiation would span multiple rounds (see issue #882) for details.
gix level.
This is merely a debug tool to learn about generation numbers.
All commit-graph commands now operate on a repository.gix --trace to also print tree-like instrumentation
gix fetch --open-negotiation-graph[=limit]
Open the negotiation graph as SVG, after optionally specifying a limit
as rendering/layouting can be very slow.
It's useful to see how the negotiation algorithm is reasoning about each commit.
gix fetch --negotiation-info to provide additional information about the negotiation phase.
bit revision list --svg to create a visual graph of commits.
It's mainly a test of how well layout-rs performs.
clippy::redundant-closure-for-method-calls lintClippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gitoxide publishable again (c16b1df)corpus --dry-run and --task-sql-suffix and --repo-sql-suffix (4cef57d)gix-trace (bd6e3d7)gix --trace to also print tree-like instrumentation (c494cfd)gitoxide version according to what's in git (83f6466)gix fetch --open-negotiation-graph[=limit] (452ed6b)gix fetch --negotiation-info to provide additional information about the negotiation phase. (096838f)gix docs available when using cargo doc (518159d)bit revision list --svg to create a visual graph of commits. (bd32e39)clippy::redundant-closure-for-method-calls lint (bcad5c2)gix level. (b82edc8)gix config tree (7aaaebf)
</details>commit::Ancestors::with_commit_graph(graph) to set and use a commitgraph.
That way, traversal speed is greatly improved for traversals that only need
access to parents and commit time, while still being more efficient if it
saves the caller to retrieve a commit again to parse it for parents.<csr-id-8d7b62736848841e0577aa0498eb39aec492a2fa/> gix_traverse::commit::Ancestors now returns rich commit information.
As part of the iteration, it will decode part of the commit and read parents and possibly
the commit time if time-based sorting is desired. These values will now be made available
instead of just the id of the commit.
This saves the caller time to parse the commit again in case it needs similar information.
<csr-id-affc9df48e7b7540a95e2d6024f05b391f38c8f0/> previously the commit-traversal sorted by date must have been wonky & rename Sorting::Topological to Sorting::BreadthFirst.
This is now fixed by using a proven data structure, the BinaryHeap as priority
queue.
The rename is to differentiate git log --topo-order from what we are doing, which is actually quite
different.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
2560a2c)298f3d7)fdee9a2)commit::Ancestors::with_commit_graph(graph) to set and use a commitgraph. (6c5c66e)Sorting::Topological to Sorting::BreadthFirst. (affc9df)gix_traverse::commit::Ancestors now returns rich commit information. (8d7b627)
</details>The main attraction of this release is support for multi-round negotiations thanks to support for the standard negotiations algorithms. Further, gix i
The main attraction of this release is support for multi-round negotiations thanks to support for the standard negotiations algorithms.
Further, gix index entries now lists attributes as well, and there is the new gix attribute query sub-command in the vain of git check-attrs.
gix attributes validate to validate attributes and ignore against git as baseline.
Use this command to test the entire index for ignored paths and their attributes and use
git check-attr and git check-ignore to validate that git agrees. Collect all
mismatches and print them.--statistics for gix excludes query
With it one gets some insights into the work done to fulfil the query.gix attribute query as something similar to git check-attrs.no-repo index from-list to create an index with empty files from the given list.
The list could be created with find . -type f for example.gitoxide on docs.rs<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
just fmt (ffc1276)gix (7983f6f)gix attributes validate to validate attributes and ignore against git as baseline. (e1fcc7f)--statistics for gix excludes query (450b232)gix attribute query as something similar to git check-attrs. (bfdcb14)no-repo index from-list to create an index with empty files from the given list. (b8db207)gitoxide on docs.rs (13a0f1e)jwalk to have a better comparison. (d67551d)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
9a9fa96)8f15cec)67da689)0269eed)420553a)2578e57)dbf8aa1)3ef5c90)3eff567)9375cd7)facaaf6)4f879bf)
</details>A maintenance release without user-facing changes, just to fix installation
A maintenance release without user-facing changes, just to fix installation
Debug for commit::Sorting.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
Debug for commit::Sorting. (a70085e)91134a1)30a1a71)6ebd61e)14e64e7)8dbd0a6)b574a39)a884121)
</details>gix index entries also prints attributes.
gix index entries also prints attributes.gix clone and gix fetch with controls for shallow repositories.ein t trace-path know accepts the trace-file alias.stdout on each write, now this is done only once.gix free index entries into gix index entries.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix index entries also prints attributes. (08e8fc2)gix free index entries into gix index entries. (ca8ebdf)gix-worktree (13a070f)index.skipHash (f29f35c)gix clone and gix fetch with controls for shallow repositories. (9723e1a)ein t query (d5616b6)ein t trace-path know accepts the trace-file alias. (f93e964)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
This release adds the new ein tool query analytics engine, which maintains a database of a git repository as acceleration data structure to run useful
This release adds the new ein tool query analytics engine, which maintains a database of a git repository as acceleration data structure to run useful queries on.
It's nothing more than an MVP, and was inspired by a program to accelerate Git-Heat-Map.
ein tool query - a git analytics engine.
A tool to build and efficiently maintain a database of information contained
in a git repository, preferably the kind of information that is expensive to obtain,
in order to facilitate queries that would be prohibitive without an accelerating
data structure.gix tree entries with rev-spec support.
Previously it wanted a tree-id, now it can derive it itself.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ein tool query - a git analytics engine. (f8cc623)gix tree entries with rev-spec support. (49520d1)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ea9fd1d)e6cc618)addd789)94c99c7)8ef1cb2)
</details>add tree::Recorder::path_clone() and tree::Recorder::track_filename() builder method. That way, the recorder can be used in other applications to keep
tree::Recorder::path_clone() and tree::Recorder::track_filename() builder method.
That way, the recorder can be used in other applications to keep track of the full
path or the filename.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
2 commits contributed to the release over the course of 30 calendar days.
time improved the way one can opt-in to potential unsoundness
in their local time support, forcing the application to make that
decision at runtime.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-ebc7f47708a63c3df4415ba0e702660d976dfb3e/> <csr-id-2290d006705ff47ad780b009fe58ee422b3285af/> <csr-id-2f2d856efe733d3cf81110c0e0607d2e7c40d968/> <csr-id-1d5ab44145ccbc2064ee8cc7acebb62db82c45aa/> <csr-id-7bce49c1d27cb279b61ff51de0038e01fcf3561e/> <csr-id-cbc5b8171cdef5933d684c481300d9fcff43cf4b/> <csr-id-329d183ad4e256a4f9cdeb34589b5f3432495f79/> <csr-id-f7f136dbe4f86e7dee1d54835c420ec07c96cd78/> <csr-id-533e887e80c5f7ede8392884562e1c5ba56fb9a8/>
<csr-id-dcdf6573a90c7f9a6855aa7be8bf707b92b73ecf/> commit traversal now sorts by commit-time more thoroughly Previously the sorting was only partial as it was only among parents. Now it is full and among all currently visible commits.
That way it is similar to what git log would produce.
<csr-id-3d8fa8fef9800b1576beab8a5bc39b821157a5ed/> upgrade edition to 2021 in most crates. MSRV for this is 1.56, and we are now at 1.60 so should be compatible. This isn't more than a patch release as it should break nobody who is adhering to the MSRV, but let's be careful and mark it breaking.
Note that git-features and git-pack are still on edition 2018
as they make use of a workaround to support (safe) mutable access
to non-overlapping entries in a slice which doesn't work anymore
in edition 2021.
<csr-id-83746f613a559a86a0ea81370fca3f094bc81e35/> require Ancestors traversal find() to return Result
Previously it would return an Option and squelch legitimate errors
which already let to quite a bug hunt.
Now find() should always return the original error when finding an
existing object, and keep it around in a Box.
That way we don't add yet another type parameter.
Performance implications are measurable, but marginable. The error type might be too big which is something we can indeed look at.
<csr-id-5cf9323dbe09789e806ed55d865281298af1a11b/> rename commit::Ancestors::mode() to *::parents()
The previous name was too generic to be helpful or discoverable.
<csr-id-86a99a90eb992322099a870fbba10dddbcb80e83/> add commit::Sorting::ByCommitTimeNewestFirstCutoffOlderThan(time).
It allows to stop traversals early if all commmits to be traversed are
older than a given time.
<csr-id-6b2af578fbff43999266c2af324070b013d1699f/> Make it possible to access the current commits buffer during commit ancestor iteration. This is useful to avoid additional lookups of the same object for reading additional data from it.
Currently one needs an object cache to avoid duplciate object extraction work, with such a cache being slower than accessing the same buffer again.
<csr-id-eb36a3dda83a46ad59078a904f4e277f298a24e1/> Add sorting mode to ancestor traversal #270
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
52b38bc)e695eda)0c81769)a517e39)145103d)4a9a05f)f536bad)a0bc98c)e1861ca)58ab2ae)c857d61)6b5c394)9d6f263)719b6bd)7bce49c)6776a3f)9498816)84cb256)rust-version to 1.64 (55066ce)8c0bca3)a5869e0)41d57b9)e313112)6efd0d3)6ccc88a)c9275b9)git-testtools to gix-testtools (b65c33d)git-pack to gix-pack (1ee81ad)git-odb to gix-odb (476e2ad)git-index to gix-index (86db5e0)git-diff to gix-diff (49a163e)git-commitgraph to gix-commitgraph (f1dd0a3)git-mailmap to gix-mailmap (2e28c56)git-discover to gix-discover (53adfe1)git-lfs to gix-lfs (b9225c8)git-chunk to gix-chunk (59194e3)git-bitmap to gix-bitmap (75f2a07)git-protocol to gix-protocol (823795a)git-refspec to gix-refspec (c958802)git-revision to gix-revision (ee0ee84)git-transport to gix-transport (b2ccf71)git-credentials to gix-credentials (6b18abc)git-prompt to gix-prompt (6a4654e)git-command to gix-command (d26b8e0)git-packetline to gix-packetline (5cbd22c)git-worktree to gix-worktree (73a1282)git-traverse to gix-traverse (1781b34)git-hashtable to gix-hashtable (26a0c98)git-worktree to gix-worktree (108bb1a)git-url to gix-url (b50817a)git-date to gix-date (9a79ff2)git-attributes to gix-attributes (4a8b3b8)git-quote to gix-quote (648025b)git-config to gix-config (3a861c8)git-ref to gix-ref (1f5f695)git-lock to gix-lock (2028e78)git-tempfile to gix-tempfile (b6cc3eb)git-object to gix-object (fc86a1e)git-actor to gix-actor (4dc9b44)git-validate to gix-validate (5e40ad0)git-hash to gix-hash (4a9d025)git-features to gix-features (e2dd68a)git-glob to gix-glob (35b2a3a)git-sec to gix-sec (eabbb92)git-path to gix-path (d3bbcfc)git-config-value to gix-config-value (622b3e1)c196d20)7c846d2)1e544e8)39ed9ed)1fea18f)0e3d0a5)d679f5b)5ac9fbe)30d8ca1)e6b9906)7114bbb)c57bdde)083909b)git-testtools (4eb842c)7717170)6b9632e)95ad56c)50cb436)269d59e)bcd9654)b2c301e)e4648f8)b755b5b)c0bfb42)0e4462d)3d8fa8f)104d922)d232567)702a161)53acf25)f47c891)0699c7e)25a7726)29a043b)1f6e5ab)5869e9f)da0716f)bc64b96)51dc828)2571831)fc6b958)34e899a)cef0b51)85a3bed)2ed0ee2)cfa1440)4974eca)e2ee3de)31c2351)f7f136d)533e887)bd5f3e8)c96473d)c06ae1c)232784a)2f506c7)ce885ad)9b9ea02)6da8250)7b61506)4e7b343)e9fcb70)aa639d8)4737b1e)3c50625)085e76b)a22b1d8)598c853)349c590)654cf39)0eb2372)350df01)b612021)e58dc30)f0cbb24)b2df941)77b7cd9)40c48c3)1b76119)8f57c29)d78aab7)373cbc8)8900d69)4624725)7d2e20c)03d0660)6add377)eb36a3d)1d5ab44)d3f9227)acd3737)ec38950)f606fa9)f69b2d6)39b40c8)0e02953)59ffbd9)a474395)21541b3)bf0106e)d39fabb)1fd56ff)d4fc81f)1d508f1)49f5453)6efd90d)ab6554b)54f3541)058f68a)70e11c2)e603306)45d3934)fa5cd06)07be661)iter adjustments (461dc53)6deb012)708fc5a)2d7956a)96461ac)4684f1c)5e0edba)fbf2157)c40faca)f123f69)c67291f)7006150)b327590)e21142b)c52a491)28e58f6)a5be31c)22337ce)7453184)7ee278b)ae02dab)a77a71c)a92f1e6)866f86f)aea6cc5)7e802a0)2958145)769c649)f0c0e36)721303d)ea224e9)6a1b16a)966f058)6688073)f057aa9)5d7ee6a)f343dad)087e853)323d92f)85de287)e21f54f)684de4b)e415c5a)ecd37ee)d91b241)3fb8377)84897fd)aa6c9e6)db21062)c977eb5)f66ccd3)f7eb355)f0aeee1)3f9ee23)7d389c8)18ae6bd)6447661)cceff1c)d9514ee)60f72f5](https://One column per quarter.