From: Ted Pavlic <ted@tedpavlic.com>
To: spearce@spearce.org
Cc: git@vger.kernel.org, gitster@pobox.com, Ted Pavlic <ted@tedpavlic.com>
Subject: [PATCH 4/3] completion: More fixes to prevent unbound variable errors.
Date: Wed, 11 Feb 2009 11:18:52 -0500 [thread overview]
Message-ID: <1234369132-22063-1-git-send-email-ted@tedpavlic.com> (raw)
In-Reply-To: <1234366634-17900-4-git-send-email-ted@tedpavlic.com>
Several functions make use of "test -n" and "test -z". In many cases,
the variables being tested were declared with "local." However, several
__variables are not, and so they must be replaced with their ${__-}
equivalents.
Signed-off-by: Ted Pavlic <ted@tedpavlic.com>
---
This patch depends on:
<1234366634-17900-3-git-send-email-ted@tedpavlic.com>
"[PATCH 2/3] completion: Change "if [...]" to "if test ..." to
match git convention"
If that patch is not applied, I can submit a new patch.
contrib/completion/git-completion.bash | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index ffde82a..055e4ac 100755
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -62,7 +62,7 @@ esac
__gitdir ()
{
if test -z "${1-}"; then
- if test -n "$__git_dir"; then
+ if test -n "${__git_dir-}"; then
echo "$__git_dir"
elif test -d .git; then
echo .git
@@ -294,7 +294,7 @@ __git_remotes ()
__git_merge_strategies ()
{
- if test -n "$__git_merge_strategylist"; then
+ if test -n "${__git_merge_strategylist-}"; then
echo "$__git_merge_strategylist"
return
fi
@@ -380,7 +380,7 @@ __git_complete_revlist ()
__git_all_commands ()
{
- if test -n "$__git_all_commandlist"; then
+ if test -n "${__git_all_commandlist-}"; then
echo "$__git_all_commandlist"
return
fi
@@ -398,7 +398,7 @@ __git_all_commandlist="$(__git_all_commands 2>/dev/null)"
__git_porcelain_commands ()
{
- if test -n "$__git_porcelain_commandlist"; then
+ if test -n "${__git_porcelain_commandlist-}"; then
echo "$__git_porcelain_commandlist"
return
fi
--
1.6.1.2.390.gba743
next prev parent reply other threads:[~2009-02-11 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 15:37 [PATCH 0/3] completion: Convention updates and DIRTYSTATE fix Ted Pavlic
2009-02-11 15:37 ` [PATCH 1/3] completion: For consistency, changed "git rev-parse" to __gitdir calls Ted Pavlic
2009-02-11 15:37 ` [PATCH 2/3] completion: Change "if [...]" to "if test ..." to match git convention Ted Pavlic
2009-02-11 15:37 ` [PATCH 3/3] completion: Prevents GIT_PS1_DIRTYSTATE from breaking when CWD is .git Ted Pavlic
2009-02-11 16:18 ` Ted Pavlic [this message]
2009-02-11 16:28 ` [PATCH 4/3] completion: More fixes to prevent unbound variable errors Shawn O. Pearce
2009-02-11 16:26 ` [PATCH 3/3] completion: Prevents GIT_PS1_DIRTYSTATE from breaking when CWD is .git Shawn O. Pearce
2009-02-11 16:53 ` Ted Pavlic
2009-02-11 16:56 ` Junio C Hamano
2009-02-11 17:20 ` Ted Pavlic
2009-02-11 18:01 ` Shawn O. Pearce
2009-02-11 16:24 ` [PATCH 2/3] completion: Change "if [...]" to "if test ..." to match git convention Shawn O. Pearce
2009-02-11 16:36 ` Ted Pavlic
2009-02-11 17:14 ` Junio C Hamano
2009-02-11 16:46 ` Junio C Hamano
2009-02-11 16:22 ` [PATCH 1/3] completion: For consistency, changed "git rev-parse" to __gitdir calls Shawn O. Pearce
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=1234369132-22063-1-git-send-email-ted@tedpavlic.com \
--to=ted@tedpavlic.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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).