git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Re: lost again on syntax change - local repository?
Date: Sun, 27 Nov 2005 21:11:37 -0800	[thread overview]
Message-ID: <7v7jat2w6u.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <861x118r9t.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "27 Nov 2005 18:01:18 -0800")

merlyn@stonehenge.com (Randal L. Schwartz) writes:

> At this point, I'm where I was before.  And this next step worked,
> although I had to say "origin":
>
>     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
>
> Uh, say what?  /some/file/foo.git#branch is no longer legal syntax?
> Help!

If it is not absolutely necessary that you need to use Cogito,
IOW, if git barebone Porcelains are good enough for your use,
the following may be adequate.

	$ echo >.git/remotes/origin <<EOF
	URL: /path/to/remote.git/
        Push: master
        Pull: master:origin
        EOF
	$ git push origin

I said "may be" because I do not understand the sequence before
"At this point"; how your local.git is initially set up to
relate to the remoge.git.  I do not see local.git being created
by cloning remote.git.  But modulo that the above should work
fine; I do that as a cheap backup on my local machine.

  reply	other threads:[~2005-11-28  5:11 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 [this message]
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
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=7v7jat2w6u.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --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).