Confused by "skipped updates" when rebasing, restoring or abandoning commits. #7680
-
I found myself with a few expected changes and many unwanted changes in my current commit.
No problem, I'll just blow those away with a
Hmm.. that's odd. And when I look at
Okay, let me try spliting on the fileset (since everything is still in that one other directory) and abandoning:
Perfect! Now to just blow away the stuff I don't want,
🤯 My first guess was something different in I'm also not sure how to create a reproducer for this. Any suggestions on what to look at/try?
On a mac with a local filesystem. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
I can't see exactly what happened, but this seems like a pretty good clue to me:
This rename is just changing the casing of the The git file system is case-sensitive, but your APFS file system is almost certainly case-insensitive. This causes weird things to happen in both git and jj. For example, if your working copy is supposed to have two different files checked out:
The directory on disk can only have one of the two casings, so one of them must lose and be placed in the "wrong" directory. If you use |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
I can't see exactly what happened, but this seems like a pretty good clue to me:
This rename is just changing the casing of the
Dialect
directory.The git file system is case-sensitive, but your APFS file system is almost certainly case-insensitive.
This causes weird things to happen in both git and jj. For example, if your working copy is supposed to have two different files checked out:
The directory on disk can only have one of the two casings, so one of them must lose and be placed in the "wrong" directory.
If you use
jj file …