path: root/
AgeCommit message (Collapse)Author
2007-07-04Update reflog message created for stashesJunio C Hamano
A stash is about a change on top of an existing commit, and not about that commit that happened to be on which the change was created. Match the message we see in "git stash list" with the commit log message to make this clear. Signed-off-by: Junio C Hamano <> Acked-by: Uwe Kleine-König <>
2007-07-04stash: end commit log with a newlineUwe Kleine-König
If I do git cat-file commit $commitid for a commit created by stash, the next prompt starts directly after the shortlog of HEAD. Signed-off-by: Uwe Kleine-König <> Signed-off-by: Junio C Hamano <>
2007-07-03git-stash: make "save" the default action again.Junio C Hamano
Signed-off-by: Junio C Hamano <>
2007-07-03Rewrite "git-frotz" to "git frotz"Junio C Hamano
This uses the remove-dashes target to replace "git-frotz" to "git frotz". Signed-off-by: Junio C Hamano <>
2007-07-02git-stash: don't complain when listing in a repo with no stashJeff King
Previously, the git-log invocation would complain if a repo had not had any stashes created in it yet: $ git-init $ git-stash fatal: ambiguous argument 'refs/stash': unknown revision or path not in the working tree. Use '--' to separate paths from revisions Instead, we only call git-log if we actually have a refs/stash. We could alternatively create the ref when any stash command is called, but it's better for the 'list' command to not require write access to the repo. Signed-off-by: Jeff King <> Signed-off-by: Junio C Hamano <>
2007-07-02git-stash: fix "can't shift that many" with no argumentsJeff King
Signed-off-by: Jeff King <> Signed-off-by: Junio C Hamano <>
2007-07-01git-stash: require "save" to be explicit and update documentationJunio C Hamano
Signed-off-by: Junio C Hamano <>
2007-07-01Add git-stash scriptしらいしななこ
When my boss has something to show me and I have to update, for some reason I am always in the middle of doing something else, and git pull command refuses to work in such a case. I wrote this little script to save the changes I made, perform the update, and then come back to where I was, but on top of the updated commit. This is how you would use the script: $ git stash $ git pull $ git stash apply [jc: with a few fixlets from the list] Signed-off-by: Nanako Shiraishi <> Signed-off-by: Junio C Hamano <>