From: Tejun Heo <htejun@gmail.com>
To: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Peer Chen <pchen@nvidia.com>
Subject: Re: [PATCH] ahci: retry enabling AHCI a few times before spitting out WARN_ON()
Date: Thu, 24 Apr 2008 13:20:27 +0900 [thread overview]
Message-ID: <48100A8B.4000102@gmail.com> (raw)
In-Reply-To: <200804240615.23463.volker.armin.hemmann@tu-clausthal.de>
Volker Armin Hemmann wrote:
> emm, even without the double slashes I get the same message:
> git fetch git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
> upstream:upstream
> fatal: Not a git repository
>
> git fetch git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
> fatal: Not a git repository
Hmm... strange.
> git --version
git version 1.5.2.4
> git fetch -v
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
upstream:upstream
* refs/heads/upstream: same as branch 'upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev
commit: 48feb3c
--
tejun
next prev parent reply other threads:[~2008-04-24 4:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 11:52 [PATCH] ahci: retry enabling AHCI a few times before spitting out WARN_ON() Tejun Heo
2008-04-24 0:24 ` Volker Armin Hemmann
2008-04-24 1:34 ` Tejun Heo
2008-04-24 1:51 ` Volker Armin Hemmann
2008-04-24 2:57 ` Tejun Heo
2008-04-24 3:28 ` Volker Armin Hemmann
2008-04-24 3:36 ` Tejun Heo
2008-04-24 3:57 ` Volker Armin Hemmann
2008-04-24 4:01 ` Tejun Heo
2008-04-24 4:15 ` Volker Armin Hemmann
2008-04-24 4:20 ` Tejun Heo [this message]
2008-04-24 4:32 ` Volker Armin Hemmann
2008-04-25 0:17 ` Volker Armin Hemmann
2008-04-25 0:44 ` Tejun Heo
2008-04-25 1:17 ` Volker Armin Hemmann
2008-04-25 1:59 ` Tejun Heo
2008-04-25 2:40 ` Volker Armin Hemmann
2008-04-25 4:47 ` Jeff Garzik
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=48100A8B.4000102@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=pchen@nvidia.com \
--cc=volker.armin.hemmann@tu-clausthal.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.