From: Jakub Narebski <jnareb@gmail.com>
To: "Simon 'corecode' Schubert" <corecode@fs.ei.tum.de>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] Allow passing of --directory to git-am.
Date: Thu, 04 Dec 2008 11:35:41 -0800 (PST) [thread overview]
Message-ID: <m3hc5jivjo.fsf@localhost.localdomain> (raw)
In-Reply-To: <49382612.3010207@fs.ei.tum.de>
Simon 'corecode' Schubert <corecode@fs.ei.tum.de> writes:
> We need to play some shell tricks to be able to pass directory names
> which contain spaces and/or quotes.
>
> Signed-off-by: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
> ---
>
> Boyd Stephen Smith Jr. wrote:
> > I'm thinking your sed line doesn't do what you think it does.
> > You probably want something like:
> > bss@monster:~$ echo "don't" | sed -e "s/'/'\\\\''/g"
> > don'\''t
>
> Thanks, I clearly did not test this well enough.
>
> git-am.sh | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/git-am.sh b/git-am.sh
> index aa60261..3baff4e 100755
> --- a/git-am.sh
> +++ b/git-am.sh
> @@ -16,6 +16,7 @@ s,signoff add a Signed-off-by line to the commit message
> u,utf8 recode into utf8 (default)
> k,keep pass -k flag to git-mailinfo
> whitespace= pass it through git-apply
> +directory= pass it through git-apply
Shouldn't it be
+ directory= pass it through git-apply
to have it aligned like the rest of it?
By the way, your patch looks whitespace damaged, although only context
for the above chunk was wrapped...
> C= pass it through git-apply
> p= pass it through git-apply
> resolvemsg= override error message when patch failure occurs
> @@ -155,8 +156,9 @@ do
> ;;
> --resolvemsg)
> shift; resolvemsg=$1 ;;
> - --whitespace)
> - git_apply_opt="$git_apply_opt $1=$2"; shift ;;
> + --whitespace|--directory)
> + quot=$(echo "$2" | sed -e "s/'/'\\\''/g")
Why not simply use "git rev-parse --sq"?
> + git_apply_opt="$git_apply_opt $1='$quot'"; shift ;;
> -C|-p)
> git_apply_opt="$git_apply_opt $1$2"; shift ;;
> --)
> @@ -454,7 +456,7 @@ do
>
> case "$resolved" in
> '')
> - git apply $git_apply_opt --index "$dotest/patch"
> + eval git apply $git_apply_opt --index '"$dotest/patch"'
Why eval?
> apply_status=$?
> ;;
> t)
> --
> 1.6.1.rc1.45.g123ed.dirty
Hmmm...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-12-04 19:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 18:48 [PATCH] Allow passing of --directory to git-am Simon 'corecode' Schubert
2008-12-04 18:51 ` Jeff King
2008-12-04 19:27 ` Junio C Hamano
2008-12-04 22:26 ` Simon 'corecode' Schubert
2008-12-04 22:33 ` Junio C Hamano
2008-12-04 23:14 ` Junio C Hamano
2008-12-04 23:36 ` [PATCH - DONTUSE] git-am: propagate -C/-p as well Junio C Hamano
2008-12-04 23:41 ` [PATCH] Allow passing of --directory to git-am Simon 'corecode' Schubert
2008-12-05 0:11 ` Junio C Hamano
2008-12-05 0:16 ` Simon 'corecode' Schubert
2008-12-04 19:35 ` Jakub Narebski [this message]
2008-12-04 22:25 ` Simon 'corecode' Schubert
2008-12-04 22:46 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2008-12-04 17:04 Simon 'corecode' Schubert
2008-12-04 18:28 ` Boyd Stephen Smith Jr.
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=m3hc5jivjo.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=corecode@fs.ei.tum.de \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).