{"thread":{"id":"51762","subject":"Question of intent: stash push --include-untracked","startedAt":"2019-08-27T20:02:19Z","lastAt":"2019-08-27T20:02:19Z","messageCount":1,"participants":["Randall S. Becker"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"381390","messageId":"019501d55d12$534b5ca0$f9e215e0$@nexbridge.com","threadId":"51762","inReplyTo":null,"subject":"Question of intent: stash push --include-untracked","fromName":"Randall S. Becker","fromEmail":"rsbecker@nexbridge.com","sentAt":"2019-08-27T20:02:10Z","receivedAt":"2019-08-27T20:02:19Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"I'm a bit perplexed about what is intended follow a git stash push\n--include-untracked. Suppose I have files a,b,c,known modified, but only\nknown is in the index. After the stash, stash show only displays known. A\nsubsequent pop will restore a,b,c. So functionally push and pop are fine,\nbut show appears to ignores files in the stash. The log shows a previous\ncommit (dce2e3e) to the WIP stash (ab0834c) that does contain the untracked\nfiles, and git diff is happy to show the contents when using the ref\ndirectly. It is just counterintuitive for stash show not to display all\nentries previously pushed. I would have expected symmetry. Is this new, or\nintended.\n\n*-.   ab0834c (refs/stash) WIP on master: bf223fc Updated known\n|\\ \\\n| | * dce2e3e untracked files on master: bf223fc Updated known\n| * a5ad1ef index on master: bf223fc Updated known\n|/\n* bf223fc (HEAD -> master) Updated known\n* db0efd4 (origin/master, origin/HEAD) initial\n\nThis on git 2.23.0\n\nThanks,\nRandall\n\n-- Brief whoami:\n NonStop developer since approximately 211288444200000000\n UNIX developer since approximately 421664400\n-- In my real life, I talk too much.\n\n\n\n"}]}