DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2009-11-12 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 --- Comment #13 from m...@mattmccutchen.net 2009-11-12 22:16 CST --- I rediscovered this bug just now and thought I would comment on what happened so it doesn't stand as a blemish on the community. Wayne and Egmont disagreed on the

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-03-16 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 --- Comment #12 from [EMAIL PROTECTED] 2006-03-16 04:52 MST --- I do agree that there are cirsumstances when fuzzy doesn't speed up things, or actually causes huge performance regression. On the other hand, as I described, there are

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-03-15 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 --- Comment #11 from [EMAIL PROTECTED] 2006-03-15 10:27 MST --- I appreciate than in your specific circumstance that an enhance behavior of --fuzzy would be useful. My testing of the --fuzzy option has also included large transfers with

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-03-14 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 --- Comment #10 from [EMAIL PROTECTED] 2006-03-14 05:46 MST --- Dear Wayne, To comment #8: If you'd say it's too hard to fix it, we have no resources to implement this or something similar, then I'd most likely accept it. But your

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-03-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 [EMAIL PROTECTED] changed: What|Removed |Added Status|CLOSED |REOPENED Resolution|FIXED

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-03-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-03-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 [EMAIL PROTECTED] changed: What|Removed |Added Status|CLOSED |REOPENED Resolution|FIXED

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-03-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-03-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3392 --- Comment #9 from [EMAIL PROTECTED] 2006-03-13 11:20 MST --- One way to manualy optimize a transfer for a new directory that is related to an old directory is to first copy the old directory using --link-dest, and then copy the new

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-01-15 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3392 --- Comment #4 from [EMAIL PROTECTED] 2006-01-15 08:19 MST --- Nice. It occurs to me that maybe the first call to do_stat should be changed to link_stat(dest_path, st, keep_dirlinks) in order to obey --keep-dirlinks when finding the

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-01-14 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3392 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-01-10 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3392 --- Comment #1 from [EMAIL PROTECTED] 2006-01-10 17:22 MST --- This behavior is a consequence of the strange logic in get_local_name in main.c. If the destination path is given as a file, then rsync uses a local name and accesses the

DO NOT REPLY [Bug 3392] fuzzy misbehaving if source is a file

2006-01-10 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3392 --- Comment #2 from [EMAIL PROTECTED] 2006-01-10 17:22 MST --- Created an attachment (id=1661) -- (https://bugzilla.samba.org/attachment.cgi?id=1661action=view) main.c from my custom rsync, showing rewritten get_local_name --