profile
viewpoint
Paul Dreik pauldreik Stockholm, Sweden https://www.pauldreik.se/ I like C++. A lot.

pauldreik/rdfind 406

find duplicate files utility

pauldreik/arduino-due-makefile 12

Arduino Due Makefile

pauldreik/safe_compare 3

Library for safe C++ integer comparisons

pauldreik/random_foreach 2

code for randomly generating all numbers in a range exactly once

pauldreik/FlintPlusPlus 1

Flint++ is cross-platform, zero-dependency port of flint, a lint program for C++ developed and used at Facebook.

pauldreik/bloaty-analyze 0

GitHub Action that executes Bloaty McBloatface.

pauldreik/Catch2 0

A modern, C++-native, header-only, test framework for unit-tests, TDD and BDD - using C++11, C++14, C++17 and later (or C++03 on the Catch1.x branch)

pauldreik/clcc 0

Fork and fixes on "The OpenCL kernel Compiler" on SourceForge

pauldreik/cppbestpractices 0

Collaborative Collection of C++ Best Practices

pauldreik/cppsandbox 0

sandbox for playing around with c++

issue commentpauldreik/rdfind

Yet another feature request - screen potential duplicates based on file size

Den 2021-11-21 kl. 22:50, skrev Seamus:

I learned of your very useful utility from some research I did some time ago. Just recently, I recommended it as a potential solution to a question on U&L SE. The OP defined |duplicate files| as files having: 1. the same file name, and 2. the same size. This seems to be an entirely reasonable definition given the files are all audio files in folders containing a music collection.

Unless I've overlooked something, it seems that |rdfind| does not have an option for using file size as a screen or criteria for duplicate detection. Instead, it has an option to calculate a /hash/checksum/ - which is certainly useful, but much more resource-intensive than file size.

And that's it - I'm making a feature request here for adding an option to screen based on file size.

Thanks for your consideration.

if rdfind encounters two files with unique file sizes, it won't consider them duplicates and therefore won't proceed with the hash calculation. Do I understand you correctly that you want to be able to optionally bypass the hash check? For this to work, one would need to also bypass the "check first bytes" and "check last bytes" check.

seamusdemora

comment created time in 15 days

created tagpauldreik/fmt

tag8.0.1_issue1824

A modern formatting library

created time in 23 days

push eventpauldreik/fmt

Victor Zverovich

commit sha 8c1b22ba6d2758a0a7a3da04c5ad42beab5b130b

Workaround a gcc 9.1 bug (#2334)

view details

Alexey Ochapov

commit sha 99768695498147627ff1c70a5c6d97d1dc7c2543

fix custom types formatting at compile-time, add test

view details

Victor Zverovich

commit sha ed2a6377e7bf1015bae50903954c24e0a285f131

Workaround msvc constexpr issues

view details

Victor Zverovich

commit sha ad97258915e5132a5d3ba98c8e70ea0f7e92fc53

Merge branch 'master' of github.com:fmtlib/fmt

view details

Daniela Engert

commit sha 70e67ae0181164b3ca935ff1b47123045aad5d8f

Re-enable module testing Prepare for compilation with gcc (modules branch).

view details

Victor Zverovich

commit sha 5a95c5ae2cccde89bd47ac02824cdb852f9951fb

Update changelog

view details

Victor Zverovich

commit sha 272660e704bf7e1be7b9cae715478065639e9a13

Remove deprecated printf functions

view details

Victor Zverovich

commit sha d338d66324058ae58ca0b6ee5970e179e9b7914e

Cleanup the printf implementation

view details

Victor Zverovich

commit sha 87876d54746f8d7f76b569d8a37343c99506266b

Cleanup the printf implementation

view details

Victor Zverovich

commit sha a04e3a2dc842be9f9a983fa45435ed46b7630d9d

Comment

view details

Victor Zverovich

commit sha 634c9487698388e4af3a4b7d52771275b4d58422

Update changelog

view details

Victor Zverovich

commit sha 622d1c0423f84641fb354c615f6edb2bb651ea9e

Update changelog

view details

Victor Zverovich

commit sha faf972f0395b4ea981a0d3514c693ed02223a797

Update docs

view details

Victor Zverovich

commit sha cbd861f188c1358b5e8a080408e76e1b9cf16bd3

Update docs

view details

Victor Zverovich

commit sha 7b9d69b827c796ee324fd96fc30772c73517e1d9

Add xchar.h to docs

view details

Владислав Щапов

commit sha f286139d22f2b6452d3206bfb9b36f09f20beddd

Fix "undefined reference to `fmt::v7::detail::basic_data<void>::digits'" Remove unused FMT_EXTERN_TEMPLATE_API

view details

Victor Zverovich

commit sha d142579e977bdcae86daf2f4d22c052e497d6651

Cleanup the format API

view details

Victor Zverovich

commit sha aa09e0f5dd30589b28aab95e53f53d519da57e6f

Update docs

view details

Victor Zverovich

commit sha 290d3f8b6179be85080b3045164c59b473734a9d

Cleanup ranges API

view details

Victor Zverovich

commit sha 760ca5ccc0667f671eba928b081f24286af2f0d4

Update docs

view details

push time in 23 days

delete branch pauldreik/oss-fuzz

delete branch : fix_boost_json_coverage_build

delete time in 23 days

PR opened google/oss-fuzz

[boost-json] fix coverage build

This is an attempt to fix the coverage build which has been broken since the initial submission. It works locally, following the https://google.github.io/oss-fuzz/advanced-topics/code-coverage/#generate-code-coverage-reports instructions.

+2 -2

0 comment

1 changed file

pr created time in a month

create barnchpauldreik/oss-fuzz

branch : fix_boost_json_coverage_build

created branch time in a month

create barnchpauldreik/simdjson

branch : fix_fuzz_build_error

created branch time in 3 months

more