From: Hauke Mehrtens <hauke@hauke-m.de>
To: mcgrof@gmail.com
Cc: linux-wireless@vger.kernel.org, Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH 3/3] compat-wireless: do not write git-clone
Date: Sun, 9 Jan 2011 16:32:21 +0100 [thread overview]
Message-ID: <1294587141-11353-4-git-send-email-hauke@hauke-m.de> (raw)
In-Reply-To: <1294587141-11353-1-git-send-email-hauke@hauke-m.de>
the command git-clone was removed and git clone should be used now.
Update error message.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
---
scripts/admin-update.sh | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/admin-update.sh b/scripts/admin-update.sh
index bf8e080..650c489 100755
--- a/scripts/admin-update.sh
+++ b/scripts/admin-update.sh
@@ -191,7 +191,7 @@ if [ -z $GIT_TREE ]; then
echo " export GIT_TREE=/home/$USER/linux-next/"
echo
echo "If you do not have one you can clone the repository:"
- echo " git-clone $GIT_URL"
+ echo " git clone $GIT_URL"
exit 1
fi
else
@@ -207,7 +207,7 @@ if [ -z $GIT_COMPAT_TREE ]; then
echo " export GIT_COMPAT_TREE=/home/$USER/compat/"
echo
echo "If you do not have one you can clone the repository:"
- echo " git-clone $GIT_COMPAT_URL"
+ echo " git clone $GIT_COMPAT_URL"
exit 1
fi
else
--
1.7.1
next prev parent reply other threads:[~2011-01-09 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 15:32 [PATCH 0/3] compat-wireless: some updates to scripts Hauke Mehrtens
2011-01-09 15:32 ` [PATCH 1/3] compat-wireless: make NEXT_TREE configurable Hauke Mehrtens
2011-01-09 15:32 ` [PATCH 2/3] compat-wireless: update patches in enable-older-kernels Hauke Mehrtens
2011-01-09 15:32 ` Hauke Mehrtens [this message]
2011-01-13 0:59 ` [PATCH 0/3] compat-wireless: some updates to scripts Luis R. Rodriguez
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=1294587141-11353-4-git-send-email-hauke@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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.
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).