From: "Evan Carroll" <me@evancarroll.com>
To: git@vger.kernel.org
Subject: Re: git-peek-remote vs git-pull (error in latter)
Date: Mon, 13 Aug 2007 17:32:06 -0500 [thread overview]
Message-ID: <428b865e0708131532x2140298dq3ac8242e51ad72c7@mail.gmail.com> (raw)
In-Reply-To: <428b865e0708131501m45b6e2f9t9926821cf93b7abc@mail.gmail.com>
It appears as if the error is from git-ls-remote which has a bug
(somewhere) in its --upload-pack
On 8/13/07, Evan Carroll <me@evancarroll.com> wrote:
> I'm having a *major* problem with git-pull and ssh locations. Notice
> the bottom works, and the top not so much can't find --upload-pack. As
> an aside, an error when people try ssh://user@location/ an error would
> be nice. die "Bad ssh-location syntax" if $cmd =~ /^ssh:/
>
> ecarroll@x60s:~/Desktop/scraper$ git pull
> --upload-pack=/home/dealermade/bin/git-upload-pack
> dealermade@chason:/home/dealermad
> /Desktop/scraper/.git
> sh: /home/dealermade/bin/git-upload-pack: not found
> fatal: The remote end hung up unexpectedly
> Cannot get the repository state from origin
>
> ecarroll@x60s:~/Desktop/scraper$ git-peek-remote
> --upload-pack=/home/dealermade/bin/git-upload-pack
> dealermade@chason:/home/dealermade/Desktop/scraper/.git
> 00af556bab4850c1f52eb259445688689f1dd4ff HEAD
> 00af556bab4850c1f52eb259445688689f1dd4ff refs/heads/master
> fe0e395cc4161071ac871215919563edc8de59c3 refs/heads/origin
>
> Please cc me in all correspondence, me@evancarroll.com
>
> Thanks again!
>
> --
> Evan Carroll
> System Lord of the Internets
> me@evancarroll.com
> 832-445-8877
>
--
Evan Carroll
System Lord of the Internets
me@evancarroll.com
832-445-8877
prev parent reply other threads:[~2007-08-13 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 22:01 git-peek-remote vs git-pull (error in latter) Evan Carroll
2007-08-13 22:32 ` Evan Carroll [this message]
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=428b865e0708131532x2140298dq3ac8242e51ad72c7@mail.gmail.com \
--to=me@evancarroll.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;
as well as URLs for NNTP newsgroup(s).