Overview
| Comment: | test(stash): pop over a changed symlink does not merge it (red) |
|---|---|
| Timelines: | family | ancestors | descendants | both | main | trunk | feat/submanifest-reader |
| Files: | files | file ages | folders |
| SHA3-256: |
d19a7ecca7cc4f79cf222cb0eb98d84a |
| User & Date: | [email protected] on 2026-10-20 01:40:58.000 |
| Other Links: | branch diff | manifest | tags |
Context
|
2026-10-20
| ||
| 01:42 |
fix(stash): do not merge a changed symlink, as fossil's stash apply does
Where a symlink was stashed or is now on disk, Apply writes the stashed file only when both are links and the link still holds the baseline. Otherwise it leaves the file and its row alone and reports it, as fossil's stash_apply prints "Cannot merge symlink" and counts a conflict. Apply and Pop now return the files they did not merge; Pop still drops the entry, as fossil's does. check-in: 2ee5684bf3 user: [email protected] tags: feat/submanifest-reader, main, trunk | |
| 01:40 | test(stash): pop over a changed symlink does not merge it (red) check-in: d19a7ecca7 user: [email protected] tags: feat/submanifest-reader, main, trunk | |
| 01:30 | test: read isLink as an integer under both drivers check-in: 179069251f user: [email protected] tags: feat/submanifest-reader, main, trunk | |
Changes
Modified internal/stash/symlink_unix_test.go
from [422d5e9af5]
to [319ff9d389].
[diff]