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.comhttp://blog.syntevo.com
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
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.
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(-)
@@ -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;;*)