From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: cutcrap?
Date: Fri, 11 Jul 2008 15:29:25 -0500 [thread overview]
Message-ID: <022201c8e394$cf876100$4ba65c90@vv507j> (raw)
In-Reply-To: <20080711141542.GJ4506@implementation.uk.xensource.com>
----- Original Message -----
From: "Samuel Thibault" <samuel.thibault@ens-lyon.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, July 11, 2008 9:15 AM
Subject: Re: cutcrap?
John Heim, le Fri 11 Jul 2008 09:12:46 -0500, a écrit :
> I'm still having problems with the speakup git repository. I'm getting a
> message saying git cannot pull head/cutcrap. The name leads me to believe
> this is something that's not supposed to be there anyway.
>
> # git-clone http://linux-speakup.org/speakup.git
> error: Couldn't get
> http://linux-speakup.org/speakup.git/refs/heads/cutcrap
> for heads/
> cutcrap
> The requested URL returned error: 404
> error: Could not interpret heads/cutcrap as something to pull
Are you perhaps using an http proxy? If so, try to disable it.
No, no proxy. But I believe this is a bug in the git-core package in debian
etch (aka stable). I have run the git-core command on several machines at
work and it had that same problem. I ran it on my machine at home and it
worked. I started investigating network issues but then it occured to me
that I'm running debian sid at home and etch at work. I upgraded a machine
to sid, tried the git-clone, and it worked.
So it's debian etch, not my network.
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
cutcrap? John Heim
` cutcrap? Samuel Thibault
` John Heim [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='022201c8e394$cf876100$4ba65c90@vv507j' \
--to=jheim@math.wisc.edu \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).