From: Petr Baudis <pasky@suse.cz>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: lost again on syntax change - local repository?
Date: Mon, 28 Nov 2005 15:34:28 +0100 [thread overview]
Message-ID: <20051128143428.GS22159@pasky.or.cz> (raw)
In-Reply-To: <86zmno6g3v.fsf@blue.stonehenge.com>
Dear diary, on Mon, Nov 28, 2005 at 02:45:24PM CET, I got a letter
where "Randal L. Schwartz" <merlyn@stonehenge.com> said that...
> >>>>> "Petr" == Petr Baudis <pasky@suse.cz> writes:
>
> Petr> It would sure be bad if this was the case. However I'm really sorry, but
> Petr> I still can't reproduce it.
>
> Reproduce by this:
>
> localhost:~/Projects/Git/Play % cg-admin-setuprepo remote.git
> localhost:~/Projects/Git/Play % mkdir local.git
> localhost:~/Projects/Git/Play % cd local.git
> localhost:..Git/Play/local.git % cg-init -minitial
> defaulting to local storage area
> Committing initial tree 4b825dc642cb6eb9a060e54bf8d69288fbee4904
> Committed as 958ed484382609786ca9ae611cc54802cb7697a9.
> localhost:..Git/Play/local.git % cg-branch-add origin "$(cd ..; pwd)/remote.git#master"
> localhost:..Git/Play/local.git % cg-push
> WARNING: I guessed the host:path syntax was used and fell back to the git+ssh protocol.
> WARNING: The host:path syntax is evil because it is implicit. Please just use a URI.
> ssh: \033]2;[zsh] localhost: No address associated with nodename
> fatal: unexpected EOF
Still works for me.
Could you patch cg-push like
diff --git a/cg-push b/cg-push
index 1d59422..bdab3b8 100755
--- a/cg-push
+++ b/cg-push
@@ -47,6 +47,7 @@ name=${ARGS[0]}
[ "$name" ] || { [ -s $_git/branches/origin ] && name=origin; }
[ "$name" ] || die "where to push to?"
uri=$(cat "$_git/branches/$name" 2>/dev/null) || die "unknown branch: $name"
+echo "using $uri"
rembranch=master
sprembranch=
@@ -54,6 +55,7 @@ if echo "$uri" | grep -q '#'; then
rembranch=$(echo $uri | cut -d '#' -f 2)
sprembranch=":$rembranch"
uri=$(echo $uri | cut -d '#' -f 1)
+ echo "now using $uri"
fi
if echo "$uri" | grep -q "^http://"; then
@@ -63,6 +65,7 @@ elif echo "$uri" | grep -q "^git+ssh://"
elif echo "$uri" | grep -q "^rsync://"; then
die "pushing over rsync not supported"
elif echo "$uri" | grep -q ":"; then
+ echo "matched ':' in $uri ?!"
echo "WARNING: I guessed the host:path syntax was used and fell back to the git+ssh protocol."
echo "WARNING: The host:path syntax is evil because it is implicit. Please just use a URI."
send_pack_update "$name" "$uri" $_git_head$sprembranch "${tags[@]}"
please?
(We are a bit careless about quoting here, which I will fix now,
but that shouldn't be the problem.)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-11-28 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 2:01 lost again on syntax change - local repository? Randal L. Schwartz
2005-11-28 5:11 ` Junio C Hamano
2005-11-28 6:36 ` Alecs King
2005-11-28 13:04 ` Randal L. Schwartz
2005-11-28 10:48 ` Petr Baudis
2005-11-28 13:09 ` Randal L. Schwartz
2005-11-28 13:41 ` Petr Baudis
2005-11-28 13:45 ` Randal L. Schwartz
2005-11-28 13:59 ` Randal L. Schwartz
2005-11-28 14:34 ` Petr Baudis [this message]
2005-11-28 14:46 ` Randal L. Schwartz
2005-11-28 19:15 ` Petr Baudis
2005-11-28 19:25 ` Randal L. Schwartz
2005-11-28 20:53 ` Petr Baudis
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=20051128143428.GS22159@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.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).