{"thread":{"id":"57185","subject":"bug when git stash apply after switching to branch with links were regular files","startedAt":"2022-01-05T00:52:58Z","lastAt":"2022-01-05T00:52:58Z","messageCount":1,"participants":["Britton Kerin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"445496","messageId":"CAC4O8c98H=txccR-3JM2L7jiAaf7WmJ1qyg+oiqSgrB5Qc1nUg@mail.gmail.com","threadId":"57185","inReplyTo":null,"subject":"bug when git stash apply after switching to branch with links were regular files","fromName":"Britton Kerin","fromEmail":"britton.kerin@gmail.com","sentAt":"2022-01-05T00:52:43Z","receivedAt":"2022-01-05T00:52:58Z","isPatch":false,"sender":{"key":"britton.kerin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/7434164?v=4"},"body":"On git version 2.34.1:\n\nI have a branch where sym links get replaced with copies of the\nregular files they point to.  If I make a change to that branch and\ngit stash it, then git checkout master again, then git stash apply I\nget messages like this:\n\n     $ git stash apply\n     Adding dirA_thats_now_a_link_again\n     Adding dirB_thats_now_a_link_again\n     etc.\n\nThese messages seem  completely spurious: applying the stash doesn't\nresult in any actual changes in any of those paths (and the links stay\nlinks).  The only change is to the actual file affected by the stash\n(which was a real file in both the branch and master).\n\nInterestingly I was getting this same message a few smallish versions\nof git back I believe when I did the checkout back to master.  I\nupdated to latest stable git and that issue went away.  So it looks\nlike maybe a fix to get rid of these spurious messages got applied in\none place but not others.\n\nIf there's interest in fixing this issue I can go back and isolate it\nmore carefully on request.\n\nBritton\n"}]}