From: Marcel Runte <marcel.runte@web.de>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Re: Kernel oops after compile error
Date: Thu, 31 Jul 2008 20:31:47 +0200 [thread overview]
Message-ID: <1905875186@web.de> (raw)
Chris Mason asked Marcel Runte:
>
> But, recent versions of Btrfs should be doing the right thing. Which
> version are you running?
>
Hi Chris,
I pulled it from here: http://www.kernel.org/hg/index.cgi/btrfs/kernel/ with latest changeset: http://www.kernel.org/hg/index.cgi/btrfs/kernel/archive/9da425337329.tar.bz2
So it must be v0.15 with your last patches included...
- Marcel
next reply other threads:[~2008-07-31 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 18:31 Marcel Runte [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-05 22:21 Re: Kernel oops after compile error Marcel Runte
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=1905875186@web.de \
--to=marcel.runte@web.de \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.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