From: "Tuncer Ayaz" <tuncer.ayaz@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH] git-fetch.sh printed protocol fix
Date: Wed, 25 Oct 2006 12:03:06 +0200 [thread overview]
Message-ID: <4ac8254d0610250303n60a6006bsa4d77aba7255485f@mail.gmail.com> (raw)
As a feature I wished for (ftp:// support in git-fetch) was added in 1.4.3
I tested that feature and found a minor logging issue. The mini-patch
below fixes that. AFAIK the pattern expansion feature I've used should
be available in any current /bin/sh. If not we will have to find another
way to print the protocol part of the used fetch URL.
--- git-core-1.4.3.2/git-fetch.sh 2006-10-24 07:29:47.000000000 +0200
+++ git-core-1.4.3.2.tma/git-fetch.sh 2006-10-25 11:44:34.000000000 +0200
@@ -310,7 +310,7 @@
done
expr "z$head" : "z$_x40\$" >/dev/null ||
die "Failed to fetch $remote_name from $remote"
- echo >&2 Fetching "$remote_name from $remote" using http
+ echo >&2 Fetching "$remote_name from $remote" using ${remote%%:*}
git-http-fetch -v -a "$head" "$remote/" || exit
;;
next reply other threads:[~2006-10-25 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 10:03 Tuncer Ayaz [this message]
2006-10-25 18:52 ` [PATCH] git-fetch.sh printed protocol fix Junio C Hamano
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=4ac8254d0610250303n60a6006bsa4d77aba7255485f@mail.gmail.com \
--to=tuncer.ayaz@gmail.com \
--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