On 26/10/10 18:59, Jim Meyering wrote:
> Jim Meyering wrote:
>> Jim Meyering wrote:
>>
>>> Pádraig Brady wrote:
On 22/10/10 18:43, Jim Meyering wrote:
> Part of reverting this change:
>
> stat now outputs the full sub-second resolution for the atime,
> mtime, and ctime
Jim Meyering wrote:
> Jim Meyering wrote:
>
>> Pádraig Brady wrote:
>>> On 22/10/10 18:43, Jim Meyering wrote:
Part of reverting this change:
stat now outputs the full sub-second resolution for the atime,
mtime, and ctime values since the Epoch, when using the %X, %Y, an
Pádraig Brady wrote:
> Actually I remember now why we didn't want --reflink
> mutually exclusive with other options.
> It's so it can be used as configuration to change
> the data copy method employed. I.E. it operates
> on much the same level as --sparse in that the
> results are mostly transparen
Actually I remember now why we didn't want --reflink
mutually exclusive with other options.
It's so it can be used as configuration to change
the data copy method employed. I.E. it operates
on much the same level as --sparse in that the
results are mostly transparent to the user.
I.E. cp could be a
Pádraig Brady wrote:
> On 26/10/10 14:54, Jim Meyering wrote:
>> Pádraig Brady wrote:
>>> On 26/10/10 12:48, Pádraig Brady wrote:
So in summary error if any of --link, --symbolic-link,
--reflink or --attributes-only are combined.
>>>
>>> I.E. leave the docs alone and do:
>>
>> Thanks. Th
Hi,
On Tue, Oct 26, 2010 at 11:39:58AM +0200, Jim Meyering wrote:
> The cp/reflink-perm test fails on a btrfs file system:
>
> echo > file2 # file with data
> cp --reflink=auto --preserve --attributes-only file2 empty_copy || fail=1
> test -s empty_copy && fail=1
>
> because with --r
Hi,
On Tue, Oct 26, 2010 at 12:57:08PM +0200, Jim Meyering wrote:
> Erik Auerswald wrote:
> > On Tue, Oct 26, 2010 at 11:39:58AM +0200, Jim Meyering wrote:
> >> The cp/reflink-perm test fails on a btrfs file system:
> >>
> >> echo > file2 # file with data
> >> cp --reflink=auto --preserve
On 26/10/10 14:54, Jim Meyering wrote:
> Pádraig Brady wrote:
>> On 26/10/10 12:48, Pádraig Brady wrote:
>>> So in summary error if any of --link, --symbolic-link,
>>> --reflink or --attributes-only are combined.
>>
>> I.E. leave the docs alone and do:
>
> Thanks. That sounds good.
> Do you feel
FYI, I considered skipping this as a known bug,
but hear that it should be fixed "soon", so prefer
to continue to see the failure until it's resolved.
>From 0960e0c83d2a79d260f2b83bb273ed13ef5bbea1 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Tue, 26 Oct 2010 16:34:51 +0200
Subject: [PATCH]
Pádraig Brady wrote:
> On 26/10/10 12:48, Pádraig Brady wrote:
>> So in summary error if any of --link, --symbolic-link,
>> --reflink or --attributes-only are combined.
>
> I.E. leave the docs alone and do:
Thanks. That sounds good.
Do you feel like writing the NEWS entry, too?
> diff --git a/sr
On 26/10/10 12:48, Pádraig Brady wrote:
> So in summary error if any of --link, --symbolic-link,
> --reflink or --attributes-only are combined.
I.E. leave the docs alone and do:
diff --git a/src/cp.c b/src/cp.c
index 5b14f3a..131a763 100644
--- a/src/cp.c
+++ b/src/cp.c
@@ -1097,9 +1097,11 @@ mai
On 26/10/10 11:57, Jim Meyering wrote:
> Erik Auerswald wrote:
>
>> Hi,
>>
>> On Tue, Oct 26, 2010 at 11:39:58AM +0200, Jim Meyering wrote:
>>> The cp/reflink-perm test fails on a btrfs file system:
>>>
>>> echo > file2 # file with data
>>> cp --reflink=auto --preserve --attributes-only fi
Erik Auerswald wrote:
> Hi,
>
> On Tue, Oct 26, 2010 at 11:39:58AM +0200, Jim Meyering wrote:
>> The cp/reflink-perm test fails on a btrfs file system:
>>
>> echo > file2 # file with data
>> cp --reflink=auto --preserve --attributes-only file2 empty_copy || fail=1
>> test -s empty_copy
The cp/reflink-perm test fails on a btrfs file system:
echo > file2 # file with data
cp --reflink=auto --preserve --attributes-only file2 empty_copy || fail=1
test -s empty_copy && fail=1
because with --reflink=auto, the file contents are copied, too,
and "empty_copy" does have nonzer
14 matches
Mail list logo
