Is there a patch submitted for this issue? I just pulled rsync-HEAD
(3.00 - cool!), and it still seems to show the same behavior.
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
On Nov 10, 2006, at 9:28 PM, Wayne Davison wrote:
On Fri, Nov 10, 2006 at 04:18:51PM +0100, Wesley W. Terpstra wrote:
However, if you sync a file that is identical in all respects except
the resource fork (xattrs), then the mtime is wrong for the first
run, but not the second (peanut->peanut2).
On Fri, Nov 10, 2006 at 04:18:51PM +0100, Wesley W. Terpstra wrote:
> However, if you sync a file that is identical in all respects except
> the resource fork (xattrs), then the mtime is wrong for the first
> run, but not the second (peanut->peanut2).
I would imagine that is because rsync didn
On Nov 10, 2006, at 3:55 PM, Wesley W. Terpstra wrote:
On Nov 10, 2006, at 11:30 AM, Matt Jenns wrote:
I'm really excited about the recent work on extended attributes. I've
compiled 2.6.9 with xattr support, and run a few tests. It seems that
if I have a file with an extended attribute ( a resou
On Nov 10, 2006, at 11:30 AM, Matt Jenns wrote:
I'm really excited about the recent work on extended attributes. I've
compiled 2.6.9 with xattr support, and run a few tests. It seems that
if I have a file with an extended attribute ( a resource fork in this
case), and I run rsync -aX , the mtime
I'm really excited about the recent work on extended attributes. I've
compiled 2.6.9 with xattr support, and run a few tests. It seems that
if I have a file with an extended attribute ( a resource fork in this
case), and I run rsync -aX , the mtime is not preserved. Example:
stat xattrsrc/a
2348
