Build a switch's aligned index entries without loading the left-out files' blobs #137
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#137
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A switch aligns the index for left-out paths with
reset <tree> -- <named paths>, which loads each differing blob from the store: about 10 s for a 2 GB left-out cache (measured with a raw-git harness, warm cache). Writing the same entries withupdate-index --index-infofrom the switch plan's mode, id and path took 0.73 s in the same harness. It needs a design that keeps the valid stamp of a left-out file that already holds the target's bytes (covered by A_left_out_file_that_already_holds_the_targets_bytes_keeps_a_valid_stamp_in_the_index), writes removal lines for named paths the target lacks, and keeps the displaced-entry detection the alignment does today (D41, LR-002). Measure on the bundled git and with a cold cache before deciding.