From: Greg Bowyer <gbowyer-97jfqw80gc69FHfhHBbuYA@public.gmane.org>
To: Kent Overstreet
<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: New stuff up in git
Date: Fri, 09 Sep 2011 23:35:35 -0700 [thread overview]
Message-ID: <4E6B0537.4060409@fastmail.co.uk> (raw)
In-Reply-To: <CAC7rs0uriXHsxKP0Z9JhZhSz5mgFG_o9hLKYnhRauFHr=2mfPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 09/09/11 15:27, Kent Overstreet wrote:
> On Fri, Sep 9, 2011 at 2:46 PM, Greg Bowyer<gbowyer-97jfqw80gc69FHfhHBbuYA@public.gmane.org> wrote:
>> Sorry if this is a dumb question, is bcache-3.1 an update to bcache for
>> kernels 3.1+
> It's the current bcache code rebased onto 3.1, yeah.
>
>> I ask because I dumbly merged bcache onto the v3.0 tag today since I want to
>> have a play with bcache
> Heh. Did you get it to compile/boot? the bcache-3.1 branch isn't
> _quite_ that far.
I did get to compile and boot, although I took the bcache branch and not
bcache-3.1 (when I say compile it wont compile if I have debugging
turned on, but I am ignoring that :S)
>> On 08/09/11 01:49, Kent Overstreet wrote:
>>> I just finished updating both the bcache (off 2.6.34) and the
>>> bcache-3.1 branches with the latest stable code.
>>>
>>> Also got cgit set up and working, finally. Need to stick a link in the
>>> wiki to it..
>>>
>>> http://evilpiepirate.org/git
>>>
>>> I still haven't figured out how to pack a git repository so cloning it
>>> doesn't take> 80% of my linode's ram, but cloning works for me so I'm
>>> done screwing with it for now.
>>>
>>> The bcache branch compiles but hasn't been tested. I don't expect any
>>> issues though, it's pretty close to what I normally develop/test on.
>>>
>>> The bcache-3.1 branch still doesn't quite compile, but it's pretty
>>> close - I'm try and get a working version pushed tomorrow, I did boot
>>> a linux 3.1 + bcache kernel at one point...
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
next prev parent reply other threads:[~2011-09-10 6:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 8:49 New stuff up in git Kent Overstreet
[not found] ` <CAC7rs0tjhf73fRGE6rvVGjiCGc1coCAZTQNFqoC0iAn+YmGZng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-08 8:56 ` Damien Churchill
[not found] ` <CAFtEh-czTh2eJXGuAH2iO=PrcAwYxayVMMYQyXUj7n6qvGtGeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-08 9:10 ` Kent Overstreet
2011-09-08 9:16 ` Damien Churchill
[not found] ` <CAFtEh-dAbCo1Ov3QZkSu8XPnmGtHNsZ3pZy3E6eA5ZTmPJ0tyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-08 14:41 ` Bostjan Skufca
2011-09-09 21:46 ` Greg Bowyer
2011-09-09 22:27 ` Kent Overstreet
[not found] ` <CAC7rs0uriXHsxKP0Z9JhZhSz5mgFG_o9hLKYnhRauFHr=2mfPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-10 6:35 ` Greg Bowyer [this message]
[not found] ` <4E6B0537.4060409-97jfqw80gc69FHfhHBbuYA@public.gmane.org>
2011-09-09 23:12 ` Kent Overstreet
[not found] ` <CAC7rs0t57Kx1f3CsQCb3CCf7r7tB6TwmwOLYVw0RJjujXAcwTw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-13 1:50 ` Greg Bowyer
[not found] ` <4E6EB6F7.9030806-97jfqw80gc69FHfhHBbuYA@public.gmane.org>
2011-09-13 0:02 ` Kent Overstreet
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=4E6B0537.4060409@fastmail.co.uk \
--to=gbowyer-97jfqw80gc69fhfhhbbuya@public.gmane.org \
--cc=kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@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