All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Buhren <robert@robertbuhren.de>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>,
	linux-btrfs@vger.kernel.org,
	Alexander Block <ablock84@googlemail.com>,
	Arne Jansen <sensille@gmx.net>
Subject: Re: [PATCH] Btrfs-progs: replace find_mount_root from send code
Date: Sat, 25 Aug 2012 10:24:31 +0200	[thread overview]
Message-ID: <50388BBF.70903@robertbuhren.de> (raw)
In-Reply-To: <20120824133348.GY17430@twin.jikos.cz>

On 24.08.2012 15:33, David Sterba wrote:
> On Thu, Aug 23, 2012 at 10:54:54AM +0200, Robert Buhren wrote:
>> I'm on linux-3.6-rc2 and btrfs-progs from git.
> Please try it with Chris' for-linus branch, it contains a fair portion
> of send-related fixes and from brief look they may be related to the
> errors you see.
>
> david
Hi David,

i just tried it with a kernel from the "for-linus" branch. But i still 
get the same error.
Just to be sure:
You ment this branch: 
http://git.kernel.org/?p=linux/kernel/git/mason/linux-btrfs.git;a=shortlog;h=refs/heads/for-linus

right?


Regards,

Robert

  reply	other threads:[~2012-08-25  8:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 10:22 Testing new send/receive: "ERROR: could not resolve root_id for" Robert Buhren
2012-08-19 14:59 ` Arne Jansen
2012-08-20 11:57 ` [PATCH] Btrfs-progs: replace find_mount_root from send code Jan Schmidt
2012-08-23  8:54   ` Robert Buhren
2012-08-24 13:33     ` David Sterba
2012-08-25  8:24       ` Robert Buhren [this message]
2012-08-27  9:16         ` Alex Lyakas
2012-08-27 18:37           ` Robert Buhren
2012-08-28  8:27             ` Alex Lyakas
2012-08-28 17:26               ` Alex Lyakas
2012-09-24 17:18                 ` David Sterba
2012-10-03 13:01   ` Alex Lyakas

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=50388BBF.70903@robertbuhren.de \
    --to=robert@robertbuhren.de \
    --cc=ablock84@googlemail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list.btrfs@jan-o-sch.net \
    --cc=sensille@gmx.net \
    /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.