From: Johannes Sixt <j.sixt@viscovery.net>
To: Thomas Singer <thomas.singer@syntevo.com>
Cc: git@vger.kernel.org
Subject: Re: git stash save <message>
Date: Fri, 05 Mar 2010 13:55:28 +0100 [thread overview]
Message-ID: <4B90FF40.4020607@viscovery.net> (raw)
In-Reply-To: <4B90F636.2030300@syntevo.com>
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
next prev parent reply other threads:[~2010-03-05 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 12:16 git stash save <message> Thomas Singer
2010-03-05 12:55 ` Johannes Sixt [this message]
2010-03-05 13:29 ` Thomas Singer
2010-03-05 16:14 ` [PATCH] stash: suggest the correct command line for unknown options Matthieu Moy
2010-03-05 17:08 ` Jeff King
2010-03-05 18:43 ` [PATCH v2] " Matthieu Moy
2010-03-07 4:01 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B90FF40.4020607@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=thomas.singer@syntevo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.