From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] Bcache fixes for 3.10
Date: Wed, 15 May 2013 01:12:41 -0700 [thread overview]
Message-ID: <20130515081241.GA16030@moria.home.lan> (raw)
In-Reply-To: <20130515080645.GC3276-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
On Wed, May 15, 2013 at 10:06:45AM +0200, Jens Axboe wrote:
> On Wed, May 15 2013, Kent Overstreet wrote:
> > Jens - couple more bcache patches. Bug fixes and a doc update.
> >
> > The following changes since commit f50efd2fdbd9b35b11f5778ed85beb764184bda9:
> >
> > Merge branch 'bcache-for-upstream' of http://evilpiepirate.org/git/linux-bcache into for-3.10/drivers (2013-05-01 09:23:05 +0200)
> >
> > are available in the git repository at:
> >
> >
> > http://evilpiepirate.org/git/linux-bcache.git bcache-for-upstream
> >
> > for you to fetch changes up to f59fce847fc8483508b5028c24e2b1e00523dd88:
> >
> > bcache: Fix error handling in init code (2013-05-15 00:48:14 -0700)
>
> No workie:
>
> axboe@nelson:/src/linux-block $ git pull
> http://evilpiepirate.org/git/linux-bcache.git bcache-for-upstream
> error: Unable to find b09beb2b52c74a69b45da259e5684e3bf3b1ca08 under
> http://evilpiepirate.org/git/linux-bcache.git
> Cannot obtain needed blob b09beb2b52c74a69b45da259e5684e3bf3b1ca08
> while processing commit 867e1162068eb5632c829d453fd65d6089564f55.
> error: Fetch failed.
Argh.
> In general, http:// git just sucks.
Yeah, but cloning over git:// seems to use a fair amount more memory
than dumb http, so that's the one I publish :/ But I do have git daemon
running, try this:
git://evilpiepirate.org/~kent/linux-bcache.git bcache-for-upstream
> If you can't host git:// on your own
> box, please consider moving to a kernel.org or similar hosting.
I'd love to not have to deal with this stuff anymore, do you know who
gives those out?
next prev parent reply other threads:[~2013-05-15 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 7:53 [GIT PULL] Bcache fixes for 3.10 Kent Overstreet
[not found] ` <20130515075302.GA26662-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-05-15 8:06 ` Jens Axboe
[not found] ` <20130515080645.GC3276-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2013-05-15 8:12 ` Kent Overstreet [this message]
[not found] ` <20130515081241.GA16030-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-05-15 8:38 ` Jens Axboe
[not found] ` <20130515083851.GH3276-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2013-05-15 13:16 ` Konstantin Ryabitsev
-- strict thread matches above, loose matches on Subject: below --
2013-04-30 19:52 Kent Overstreet
[not found] ` <20130430195214.GH9931-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-05-01 7:26 ` Jens Axboe
2013-05-01 18:54 ` Kent Overstreet
[not found] ` <20130501185450.GA4057-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-05-01 19:05 ` Jens Axboe
[not found] ` <20130501190553.GC7800-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2013-05-01 21:19 ` Kent Overstreet
2013-05-02 6:10 ` Jens Axboe
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=20130515081241.GA16030@moria.home.lan \
--to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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