Github messages for voidlinux
 help / color / mirror / Atom feed
From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rdfind: update to 1.5.0.
Date: Fri, 29 Oct 2021 06:24:02 +0200	[thread overview]
Message-ID: <20211029042402.Sg9PqRLahq4asQo-f-K90WFFvEoxUExGwXYiwqiLcDs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33763@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

New comment by zdykstra on void-packages repository

https://github.com/void-linux/void-packages/pull/33763#issuecomment-954419152

Comment:
Tested locally under `x86_64/glibc`, no surprises here.

```
$ rdfind -n true .
(DRYRUN MODE) Now scanning ".", found 47342 files.
(DRYRUN MODE) Now have 47342 files in total.
(DRYRUN MODE) Removed 777 files due to nonunique device and inode.
(DRYRUN MODE) Total size is 17896647200 bytes or 17 GiB
Removed 8584 files due to unique sizes from list. 37981 files left.
(DRYRUN MODE) Now eliminating candidates based on first bytes: removed 31697 files from list. 6284 files left.
(DRYRUN MODE) Now eliminating candidates based on last bytes: removed 1741 files from list. 4543 files left.
(DRYRUN MODE) Now eliminating candidates based on sha1 checksum: removed 532 files from list. 4011 files left.
(DRYRUN MODE) It seems like you have 4011 files that are not unique
(DRYRUN MODE) Totally, 9 MiB can be reduced.
(DRYRUN MODE) Now making results file results.txt
 $ pwd
/home/zdykstra/source/void-packages
$ rdfind -v
This is rdfind version 1.5.0
```

  parent reply	other threads:[~2021-10-29  4:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 14:18 [PR PATCH] " jhe2
2021-10-29  2:57 ` ericonr
2021-10-29  4:24 ` zdykstra [this message]
2021-10-29  7:11 ` [PR PATCH] [Updated] " jhe2
2021-10-29  7:12 ` jhe2
2021-10-29 11:48 ` [PR PATCH] [Merged]: " sgn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211029042402.Sg9PqRLahq4asQo-f-K90WFFvEoxUExGwXYiwqiLcDs@z \
    --to=zdykstra@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).