Bug Fixes
-
always update modification date when packed refs are forcefully reloaded.
The latter happens right after the file was written, which means we
definitely have to update our modification date or else the buffer
will be read again next time somebody asks for an up-to-date version.The ordering of operations is such that at worst, the buffer is loaded
again instead of keeping an outdated version of it, which would happen
if the metadata is read afterwards.
Commit Statistics
- 17 commits contributed to the release over the course of 26 calendar days.
- 26 days passed between releases.
- 1 commit where understood as conventional.
- 1 unique issue was worked on: #427
Thanks Clippy
Clippy helped 2 times to make code idiomatic.
Commit Details
view details
- #427
- make fmt (4b320e7)
- adapt to changes in git-features (777b40c)
- Adjust to changes in
git-features
(07168c7) - Use generalized reload-on-demand in
git-ref
(8d0cce7) - Now it's possible to update packed refs using the shared code (78222c2)
- The first step towards using the generalized
ReloadIfChanged
in git-ref (e8de0ef) - always update modification date when packed refs are forcefully reloaded. (1d20035)
- Uncategorized
- prepare changelogs prior to reelase (c06ae1c)
- Release git-hash v0.9.7, git-features v0.22.1 (232784a)
- Merge branch 'format_git_date_time' (99e12be)
- thanks clippy (4bd747c)
- Merge branch 'write-index-files' into write-index-v2 (cddc2ca)
- Merge branch 'write-index-files' into rev-parse-delegate (370110d)
- thanks clippy (763cec8)
- Merge branch 'main' into rev-parse-delegate (4ae2bed)
- Merge branch 'main' into rev-parse-delegate (6da8250)
- Fix typos (e9fcb70)