| commit | 10ab302abd1b091bdf48e286b67d671187166dea | |
| author | Sam Liddicott <sam@liddicott.com> | |
| Wed, 12 Nov 2008 08:35:33 +0000 (12 08:35 +0000) | ||
| committer | Sam Liddicott <sam@liddicott.com> | |
| Wed, 10 Dec 2008 10:10:58 +0000 (10 10:10 +0000) | ||
| tree | 9c8e41f471660b9136a0572efe70d74dc3abdee4 | treesnapshot (tar.gz zip) |
| parent | e38eb1a586813c71d8f3eeffd0a8781e4dcdbe96 | commitdiff |
Consider when find-next doesn't continue from find-first exactly
In some cases, especially with current ffirst/fntext ntrans problems where some
data is lost, the findnext doesn't carry one xactly from where findfirst left
off, and so some data is duplicated.
This fix tries to prevent that
In some cases, especially with current ffirst/fntext ntrans problems where some
data is lost, the findnext doesn't carry one xactly from where findfirst left
off, and so some data is duplicated.
This fix tries to prevent that
| source4/ntvfs/proxy/vfs_proxy.c | diffblobblamehistory |