{"thread":{"id":"50315","subject":"git stash changes ORIG_HEAD","startedAt":"2019-01-25T00:23:11Z","lastAt":"2019-01-25T00:23:11Z","messageCount":1,"participants":["Norbert Kiesel"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"367631","messageId":"CAM+g_NvpqPJusmwt1ODQcFhOmphs2U_fkPPxwzv540-6ON=PJw@mail.gmail.com","threadId":"50315","inReplyTo":null,"subject":"git stash changes ORIG_HEAD","fromName":"Norbert Kiesel","fromEmail":"nkiesel@gmail.com","sentAt":"2019-01-25T00:22:58Z","receivedAt":"2019-01-25T00:23:11Z","isPatch":false,"sender":{"key":"nkiesel@gmail.com","avatar":null},"body":"Hi,\n\nI monitor a couple of Git repos by reviewing changes via:\n\n% git pull\n% git log -p -w --no-merges ORIG_HEAD..\n\nThis works wonderfully for me.  However, sometimes I have pending\nchanges in my repo (because I did not yet committed them to a new\nbranch).  I thought I could simply use\n\n% git pull --rebase --autostash\n% git log -p -w --no-merges ORIG_HEAD..\n\nHowever, this does not work as intended because stashing moves\nORIG_HEAD.  Right now I use\n\n% orig=$(git rev-parse HEAD)\n% git pull --rebase --autostash\n% git log -p -w --no-merges orig..\n\nIs it really necessary that ORIG_HEAD is moved while stashing? This\ndoes defeat it's purpose because it's always identical to HEAD after\nthe stash is applied. Or could we have an option to not do that? Or is\nthere already another symbolic\nname I could use?\n\nBest,\n  Norbert\n"}]}