From: "Aurélien Aptel" <aaptel@suse.com>
To: Karel Zak <kzak@redhat.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: hardlink util -- files de-duplication
Date: Fri, 01 Jun 2018 15:25:48 +0200 [thread overview]
Message-ID: <87lgby1vvn.fsf@suse.com> (raw)
In-Reply-To: <20180601113807.ghf6dtcd5xa6qptu@ws.net.home>
Karel Zak <kzak@redhat.com> writes:
> Comments & objections?
Not objecting but I feel like I should mention there are multiple
well-established alternatives:
https://github.com/tobiasschulz/fdupes
http://freedup.org/
https://rdfind.pauldreik.se/
https://github.com/markfasheh/duperemove
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2018-06-01 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 11:38 hardlink util -- files de-duplication Karel Zak
2018-06-01 13:08 ` Ruediger Meier
2018-06-01 20:20 ` Kevin Fenzi
2018-06-02 0:00 ` Francisco J. Tsao Santin
2018-06-01 13:25 ` Aurélien Aptel [this message]
2018-06-01 13:45 ` Samuel Thibault
2018-06-06 12:02 ` Carlos Santos
2018-06-01 13:29 ` Dmitry V. Levin
2018-06-12 10:55 ` Karel Zak
2018-06-12 11:22 ` Ruediger Meier
2018-06-12 12:12 ` Karel Zak
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=87lgby1vvn.fsf@suse.com \
--to=aaptel@suse.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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).