From: Gerhard Wiesinger <lists@wiesinger.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] git.qemu.org problem, down?
Date: Sun, 3 Apr 2011 21:55:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1104032154280.1935@bbs.intern> (raw)
In-Reply-To: <4D98CEF2.2030808@codemonkey.ws>
On Sun, 3 Apr 2011, Anthony Liguori wrote:
> On 04/03/2011 12:46 PM, Gerhard Wiesinger wrote:
>> Hello,
>>
>> I'm having problems accessing git.qemu.org since days. Is it moved or down?
>
> No, you can git pull/push from it just fine. It's just not running a git
> browser ATM.
git pull fatal: http://git.qemu.org/qemu.git/info/refs not found: did you
run git update-server-info on the server?
It worked well from that checkout, nothing changed here.
Thnx.
Ciao,
Gerhard
--
http://www.wiesinger.com/
next prev parent reply other threads:[~2011-04-03 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 17:46 [Qemu-devel] git.qemu.org problem, down? Gerhard Wiesinger
2011-04-03 19:48 ` Anthony Liguori
2011-04-03 19:55 ` Gerhard Wiesinger [this message]
2011-04-03 20:06 ` Stefan Weil
2011-04-04 1:02 ` Anthony Liguori
2011-04-07 18:58 ` Gerhard Wiesinger
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=alpine.LFD.2.02.1104032154280.1935@bbs.intern \
--to=lists@wiesinger.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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).