I'm still fairly new to git (coming from svn) and have found `git stash` to be
really useful for storing in-progress work to resume later, as one might
otherwise do with diff/patch files. (With the git tools I use, I find `git
stash pop` to be more convenient and reliable than creating and
On Mon, Apr 13, 2015 at 02:24:04PM -0700, Quinn Taylor wrote:
I'm still fairly new to git (coming from svn) and have found `git stash` to
be really useful for storing in-progress work to resume later, as one might
otherwise do with diff/patch files. (With the git tools I use, I find `git
Quinn:
On Mon, Apr 13, 2015 at 5:24 PM, Quinn Taylor quinntay...@mac.com wrote:
I'm still fairly new to git (coming from svn) and have found `git stash` to
be really useful for storing in-progress work to resume later, as one might
otherwise do with diff/patch files. (With the git tools I
Trevor:
On Mon, Apr 13, 2015 at 9:44 PM, Trevor Saunders tbsau...@tbsaunde.org wrote:
I would expect the answers to be it sets the working directories state
to the state in HEAD, and leaves untracked files alone. If that's what
you want you can do git commit -m message; git reset --hard; git
On Mon, Apr 13, 2015 at 10:05:02PM -0400, Brandon McCaig wrote:
Trevor:
On Mon, Apr 13, 2015 at 9:44 PM, Trevor Saunders tbsau...@tbsaunde.org
wrote:
I would expect the answers to be it sets the working directories state
to the state in HEAD, and leaves untracked files alone. If that's
5 matches
Mail list logo
