From: Eli Zaretskii <eliz@gnu.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 9480@debbugs.gnu.org
Subject: bug#9480: 24.0.50; (vc-git) stash@{n} - requires shell quoting?
Date: Mon, 12 Sep 2011 06:51:30 -0400 [thread overview]
Message-ID: <E1R346s-0005ee-LZ@fencepost.gnu.org> (raw)
In-Reply-To: <81d3f6t9jn.fsf@gmail.com> (message from Jambunathan K on Mon, 12 Sep 2011 14:35:48 +0530)
> From: Jambunathan K <kjambunathan@gmail.com>
> Cc: 9480@debbugs.gnu.org
> Date: Mon, 12 Sep 2011 14:35:48 +0530
>
> | Running git stash show -p stash@{0} . in background... done
> `----
>
> But in the *vc-git-stash* buffer I see the following message
>
> ,---- *vc-git-stash*
> | '-p stash@0' is not a stash
> `----
>
> Not the absence of `{' `}' in the error report. I hope that provides
> some clue on what the underlying git sees.
Yes, I see the problem, but now I wonder how come users of Posix
platforms didn't see it. Does it happen if your shell-file-name is
set to "sh", not "bash" (assuming the Cygwin Bash comes with such an
executable or a link)?
Perhaps someone who uses this on Unix or GNU system could try this
command and see if it needs quoting in general, not just on Windows
with Cygwin Bash.
next prev parent reply other threads:[~2011-09-12 10:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 7:09 bug#9480: 24.0.50; (vc-git) stash@{n} - requires shell quoting? Jambunathan K
2011-09-12 7:29 ` Eli Zaretskii
2011-09-12 9:05 ` Jambunathan K
2011-09-12 10:51 ` Eli Zaretskii [this message]
2011-09-12 11:22 ` Jambunathan K
2011-09-12 11:50 ` Antoine Levitt
2011-09-12 11:56 ` Eli Zaretskii
2011-09-13 4:46 ` Jambunathan K
2011-09-13 1:39 ` Richard Stallman
2011-09-13 4:03 ` Glenn Morris
2011-09-13 4:37 ` Eli Zaretskii
2011-09-13 5:14 ` Jambunathan K
2011-09-13 6:17 ` Jambunathan K
2011-09-13 6:54 ` Eli Zaretskii
2011-09-13 18:05 ` Stefan Monnier
2011-09-13 13:35 ` Stefan Monnier
2011-09-13 15:27 ` Eli Zaretskii
2011-09-13 18:21 ` Glenn Morris
2011-09-14 10:58 ` Jambunathan K
2011-09-14 11:57 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1R346s-0005ee-LZ@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=9480@debbugs.gnu.org \
--cc=kjambunathan@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).