Hi folks, I'm just checking in case I'm missing something: Is there any way to tell "git stash create" to include untracked files? Someone recently brought up a situation where they'd like to take a working directory state (incl untracked but not-ignored files), and reproduce it in another working directory on another machine; "git stash create" seems to be ideal for this purpose, save for the (apparent) lack of arguments support. If this is not possible today and we wanted to better support this usecase, what would be a sensible way to do it? I can see three possible directions: 1) Change the "create" subcommand to treat specific options as options rather than the stash message (and make it understand -u / --include-untracked) 2) Create a new subcommand like "create" that actually supported relevant options (--include-untracked, --staged, maybe also pathspecs), without changing the contract of "create" 3) Add an option to the "save" subcommand, asking it to actually leave the working tree untouched (like create does) - and then expect the user of this usecase to "drop". It's possible to just use the existing "push" and then immediately "pop", but the resulting temporary changes to the working tree could make things like IDEs go into an unhappy indexing frenzy, depending on the amount of local change. I realize there's the "make stashes refs" work ongoing that's related to this, but I don't think I've seen anything there that directly addresses this "make my local changes be available over there *without* touching my working tree" requirement. Thanks, Tao
