No need to explicitly position fd - dedup - deduplicating backup program
HTML git clone git://bitreich.org/dedup/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/dedup/
DIR Log
DIR Files
DIR Refs
DIR Tags
DIR README
DIR LICENSE
---
DIR commit 79255b6852407b7ba71207ead1e22887eca3e664
DIR parent 6ff2339d17de2f963e216f164275cf0b96a1e206
HTML Author: sin <sin@2f30.org>
Date: Tue, 26 Feb 2019 11:21:56 +0000
No need to explicitly position fd
It is the responsibility of the caller to make sure that fd is
positioned correctly. This is to be consistent with the way we walk
the cache.
Diffstat:
M dedup.c | 1 -
1 file changed, 0 insertions(+), 1 deletion(-)
---
DIR diff --git a/dedup.c b/dedup.c
@@ -405,7 +405,6 @@ walk_snap(int (*fn)(struct snapshot *, void *), void *arg)
{
uint64_t i;
- xlseek(ifd, SNAPHDR_LEN, SEEK_SET);
for (i = 0; i < snaphdr.nr_snapshots; i++) {
struct snapshot *snap;
int ret;