git stash save <message>

6 messages, 4 authors, 2016-06-15 · open the first message on its own page

git stash save <message>

From: Thomas Singer <hidden>
Date: 2016-06-15 22:48:23

Where can I find information about what content in <message> is (not)
allowed? We've got a bug-report where a SmartGit user has simply entered a
minus and Git refused to work. Of course, entering just a minus is quite
useless, but we have to be able to reliable detect allowed and disallowed
messages. Should every message with a leading minus be rejected? Maybe the
best would be to add a new command line option, e.g. --message before the
<message>, so one can provide anything as message?

--
Best regards,
Thomas Singer
=============
syntevo GmbH
http://www.syntevo.com
http://blog.syntevo.com

Re: git stash save <message>

From: Johannes Sixt <hidden>
Date: 2016-06-15 22:48:23

Thomas Singer schrieb:
Where can I find information about what content in <message> is (not)
allowed? We've got a bug-report where a SmartGit user has simply entered a
minus and Git refused to work. Of course, entering just a minus is quite
useless, but we have to be able to reliable detect allowed and disallowed
messages.
Does SmartGit call 'git stash save' behind the scenes with the
user-supplied message? Then it should run

  git stash save -- "$msg"

and you don't need to forbid anything.

-- Hannes

Re: git stash save <message>

From: Thomas Singer <hidden>
Date: 2016-06-15 22:48:23

On 05.03.2010 13:55, Johannes Sixt wrote:
Does SmartGit call 'git stash save' behind the scenes with the
user-supplied message? Then it should run

  git stash save -- "$msg"

and you don't need to forbid anything.
Thank you very much, this solved the problem.

Tom

[PATCH] stash: suggest the correct command line for unknown options.

From: Matthieu Moy <hidden>
Date: 2016-06-15 22:48:23

Signed-off-by: Matthieu Moy <redacted>
---
quoted
Does SmartGit call 'git stash save' behind the scenes with the
user-supplied message? Then it should run

  git stash save -- "$msg"

and you don't need to forbid anything.
Thank you very much, this solved the problem.
... unless one considers that the problem is that you had to ask.
Something like this should avoid others the problem.

 git-stash.sh |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/git-stash.sh b/git-stash.sh
index 2d69196..cf4e673 100755
--- a/git-stash.sh
+++ b/git-stash.sh
@@ -151,6 +151,7 @@ save_stash () {
 			;;
 		-*)
 			echo "error: unknown option for 'stash save': $1"
+			echo "       To provide a message, use 'git stash -- $1'."
 			usage
 			;;
 		*)
-- 
1.7.0.231.g9fa6.dirty

Re: [PATCH] stash: suggest the correct command line for unknown options.

From: Jeff King <hidden>
Date: 2016-06-15 22:48:23

On Fri, Mar 05, 2010 at 05:14:53PM +0100, Matthieu Moy wrote:
quoted hunk
diff --git a/git-stash.sh b/git-stash.sh
index 2d69196..cf4e673 100755
--- a/git-stash.sh
+++ b/git-stash.sh
@@ -151,6 +151,7 @@ save_stash () {
 			;;
 		-*)
 			echo "error: unknown option for 'stash save': $1"
+			echo "       To provide a message, use 'git stash -- $1'."
Don't you mean "git stash save -- $1"?

-Peff

[PATCH v2] stash: suggest the correct command line for unknown options.

From: Matthieu Moy <hidden>
Date: 2016-06-15 22:48:23

Signed-off-by: Matthieu Moy <redacted>
---
Oups, as noticed by peff, my proposed command was wrong ...

 git-stash.sh |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/git-stash.sh b/git-stash.sh
index 2d69196..aa47e54 100755
--- a/git-stash.sh
+++ b/git-stash.sh
@@ -151,6 +151,7 @@ save_stash () {
 			;;
 		-*)
 			echo "error: unknown option for 'stash save': $1"
+			echo "       To provide a message, use git stash save -- '$1'"
 			usage
 			;;
 		*)
-- 
1.7.0.231.g9fa6.dirty
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help