From: Christoph Hellwig <hch@infradead.org>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: Lukas Czerner <lczerner@redhat.com>,
linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: fix 251's cp -axT problem
Date: Wed, 11 Jan 2012 06:45:44 -0500 [thread overview]
Message-ID: <20120111114544.GE14423@infradead.org> (raw)
In-Reply-To: <1326195560-4434-1-git-send-email-liubo2009@cn.fujitsu.com>
On Tue, Jan 10, 2012 at 07:39:20PM +0800, Liu Bo wrote:
> When I ran xfstests, 251 got failed cause "cp -axT" did not work as wish:
> cp: cannot overwrite directory `/mnt/scratch/1' with non-directory
>
> With this patch, 251 has passed.
Why would cp give that message with a missing /?
I'm not against putting this in, but I'd like to understand what's going
on.
Lukas, any idea?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-11 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 11:39 [PATCH] xfstests: fix 251's cp -axT problem Liu Bo
2012-01-11 11:45 ` Christoph Hellwig [this message]
2012-01-11 12:14 ` Lukas Czerner
2012-01-12 1:16 ` Liu Bo
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=20120111114544.GE14423@infradead.org \
--to=hch@infradead.org \
--cc=lczerner@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
--cc=xfs@oss.sgi.com \
/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