{"thread":{"id":"54075","subject":"Inconsistent error message with git checkout","startedAt":"2020-08-20T18:27:52Z","lastAt":"2020-08-20T18:27:52Z","messageCount":1,"participants":["Chris DeCarolis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"404108","messageId":"CAMs-bDiFmD3=rWVc33oD-rUYWfawAjeqtbgsfoYzq9cav9UCsQ@mail.gmail.com","threadId":"54075","inReplyTo":null,"subject":"Inconsistent error message with git checkout","fromName":"Chris DeCarolis","fromEmail":"chris@elementl.com","sentAt":"2020-08-20T18:27:34Z","receivedAt":"2020-08-20T18:27:52Z","isPatch":false,"sender":{"key":"chris@elementl.com","avatar":null},"body":"Hello,\n\nI hope all is well. I wanted to send this email to report a possible\ninconsistency with the error message displayed by git checkout under\ncertain conditions.\n\nWhen I try to switch branches using git checkout, and switching is\ndisallowed due to uncommitted changes, the error message will tell me\nthe absolute path of the files causing the issue rather than the\nrelative path. This seems to be a bit inconsistent, as calling git\nstatus, for example, will display relative paths. Since this only\noccurs when barred from actually switching branches, it seems\ndisplaying the relative path would be a better option here.\n\nI'd love to know your thoughts as to whether changing this behavior is\nworthwhile or not.\n\nBest,\nChris\n"}]}