From: Darren Hart <dvhart@linux.intel.com>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: Darren Hart
<public-dvhart-VuQAYsv1563Yd54FQh9/CA@plane.gmane.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 7/8] oe-git-proxy.sh: Add a new comprehensive git proxy script
Date: Tue, 05 Feb 2013 08:20:16 -0800 [thread overview]
Message-ID: <51113140.5050600@linux.intel.com> (raw)
In-Reply-To: <ly7gmn57tl.fsf@ensc-virt.intern.sigma-chemnitz.de>
On 02/05/2013 03:16 AM, Enrico Scholz wrote:
>
>
> Darren Hart <dvhart-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> writes:
>
>> + $NC -X connect $*
>
> why '$*' but not '"$@*"'?
>
>
>> +$NC $METHOD $*
>
> ditto
I'm not familiar with $@*
As for $* versus $@, the issue is how the arguments are presented. $* as
a single word, $@ each argument is quoted separately. I believe I ran
into issues with $@. I haven't had any trouble with $*. Is there a
particular use case where you can see this failing as is?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-02-05 16:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 10:31 [PATCH 0/8] Git fetcher and proxy handling updates Darren Hart
2013-02-05 10:31 ` [PATCH 1/8] bitbake: fetch2: Print the complete SRCREV variable name when INVALID Darren Hart
2013-02-05 10:31 ` [PATCH 2/8] bitbake: fetch2: Export upper and lower case environment variables Darren Hart
2013-02-05 10:31 ` [PATCH 3/8] bitbake: fetch2: Remove broken git variables from the environment Darren Hart
2013-02-05 10:31 ` [PATCH 4/8] oe-buildenv-internal: Remove GIT variables from BB_ENV_EXTRAWHITE Darren Hart
2013-02-05 10:31 ` [PATCH 5/8] oe-buildenv-internal: Add upper and lower case proxy vars to BB_ENV_EXTRAWHITE Darren Hart
2013-02-05 10:31 ` [PATCH 6/8] base.bbclass: Remove generate_git_config() Darren Hart
2013-02-05 10:31 ` [PATCH 7/8] oe-git-proxy.sh: Add a new comprehensive git proxy script Darren Hart
2013-02-05 11:16 ` Enrico Scholz
2013-02-05 16:20 ` Darren Hart [this message]
2013-02-05 16:36 ` Enrico Scholz
2013-02-05 17:44 ` Darren Hart
2013-02-05 18:40 ` Otavio Salvador
2013-02-05 18:50 ` Darren Hart
2013-02-05 19:08 ` Enrico Scholz
2013-02-05 19:18 ` Darren Hart
2013-02-05 19:29 ` Otavio Salvador
2013-02-05 22:10 ` Richard Purdie
2013-02-05 10:31 ` [PATCH 8/8] git proxy: Document usage of oe-git-proxy.sh and remove alternatives Darren Hart
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=51113140.5050600@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=public-dvhart-VuQAYsv1563Yd54FQh9/CA@plane.gmane.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