Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine
Date: Fri, 04 Feb 2011 10:21:32 +1100	[thread overview]
Message-ID: <4D4B387C.2010500@csamuel.org> (raw)
In-Reply-To: <BfAAZL8T1uB@helmut.hullen.de>

On 03/02/11 22:46, Helmut Hullen wrote:

> I've just checked the 2.6.38-rc[1-3] ChangeLog. Only rc1
> (18.1.2011) has included many btrfs changes, neither rc2
> nor rc3 includes any btrfs change.

There have been no changes in git since either, but Chris Mason
did say he was planning on sending a pull request to Linus in
the next week or so.

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

  reply	other threads:[~2011-02-03 23:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e9vOd5LzdBK.A.dyD.h6eSNB@chimera>
     [not found] ` <-tcJxClTQPH.A.Z6D.r6eSNB@chimera>
2011-02-03 11:20   ` [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine Martin Steigerwald
2011-02-03 11:46     ` Helmut Hullen
2011-02-03 23:21       ` Chris Samuel [this message]
2011-02-03 19:05     ` Rafael J. Wysocki

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=4D4B387C.2010500@csamuel.org \
    --to=chris@csamuel.org \
    --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