Re-pin go-diskfs to latest master, drop fork replace#20
Conversation
|
@deitch this re-pins partitionresizer onto go-diskfs master, which now includes #411. Ready for review when you have a chance. |
eriknordmark
force-pushed
the
source-fsck-preflight
branch
from
4ee66b8 to
70fb698
Compare
|
Test timed out. I restarted it, but might be worth extending the test maximum time. |
The other or already extends the timeout. Marge that one first then this one after a rebase? |
|
Done. Rebase this, and you should be good to go. |
eriknordmark
force-pushed
the
source-fsck-preflight
branch
from
70fb698 to
b282e12
Compare
eriknordmark
changed the title
Bump github.com/diskfs/go-diskfs to the 2026-06-18 master tip, which now carries the ErrReReadDeferred change from diskfs/go-diskfs#411, and remove the temporary `replace => github.com/eriknordmark/go-diskfs` directive. go mod tidy also prunes the stale go.sum entries left from the fork pin. The replace was only ever meant to pin the pre-merge fork commit and be dropped once #411 landed in master. It was added in diskfs#15, where Claude broke its own rule: a temporary fork-pinning replace must be dropped before the PR merges, never carried into main. diskfs#15 merged with it still in tree, leaving upstream main depending on a personal fork; this commit removes it. Signed-off-by: eriknordmark <erik@zededa.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
eriknordmark
force-pushed
the
source-fsck-preflight
branch
from
b282e12 to
91467d9
Compare
Done. Sorry for the mess-up in #15, but I can't promise claude won't mess up again. |
I think the one thing you can promise about probabilistic engines is that they will do the same thing different ways with different outcomes each time. 😁 |
2 participants
Bump
github.com/diskfs/go-diskfsto the 2026-06-18 master tip, which now carries theErrReReadDeferredchange from diskfs/go-diskfs#411, and remove the temporaryreplace github.com/diskfs/go-diskfs => github.com/eriknordmark/go-diskfsdirective.go mod tidyalso prunes the stalego.sumentries left from the fork pin.The replace was only ever meant to pin the pre-merge fork commit and be dropped once #411 landed in master. It was added in #15, where Claude broke its own rule: a temporary fork-pinning
replacemust be dropped before the PR merges, never carried intomain. #15 merged with it still in tree, leaving upstreammaindepending on a personal fork; this PR removes it and re-pins to the real master tag.