From: Ralf Baechle <ralf@linux-mips.org>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linux-mips@linux-mips.org
Subject: Re: git trouble
Date: Wed, 1 Mar 2006 17:04:18 +0000 [thread overview]
Message-ID: <20060301170418.GA22739@linux-mips.org> (raw)
In-Reply-To: <4405D0D8.7030704@am.sony.com>
On Wed, Mar 01, 2006 at 08:50:32AM -0800, Geoff Levand wrote:
> I'm having this problem lately... Any help?
>
> $ cg-clone http://www.linux-mips.org/pub/scm/linux.git linux-mips.git
> defaulting to local storage area
> 08:45:45 URL:http://www.linux-mips.org/pub/scm/linux.git/HEAD [23/23] -> "refs/heads/.origin-fetching" [1]
> error: Could not interpret ref: refs/heads/master as something to pull
> cg-fetch: objects fetch failed
> cg-clone: fetch failed
HEAD used to be a symlink; more recent versions of git which try to
support operating systems without symlinks put something like
"ref: refs/heads/master" into that file. I suspect your cogito is
simply too old to grok that.
Ralf
prev parent reply other threads:[~2006-03-01 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 16:50 git trouble Geoff Levand
2006-03-01 17:04 ` Ralf Baechle [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=20060301170418.GA22739@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=geoffrey.levand@am.sony.com \
--cc=linux-mips@linux-mips.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