From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: Alexey Gladkov <legion@altlinux.org>,
"util-linux" <util-linux@vger.kernel.org>
Subject: Re: hardlink util -- files de-duplication
Date: Tue, 12 Jun 2018 13:22:45 +0200 [thread overview]
Message-ID: <201806121322.46190.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20180612105522.byg6agpta355f73x@ws.net.home>
On Tuesday 12 June 2018, Karel Zak wrote:
> I won't have enough time in next two weeks to work on this task (fix
> indention, reuse some lib/ stuff, etc.), so any volunteer(s)? ;-)
I would do this, maybe next week or so. Should it go to sys-utils or
misc-utils?
cu,
Rudi
next prev parent reply other threads:[~2018-06-12 11:22 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
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 [this message]
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=201806121322.46190.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--cc=legion@altlinux.org \
--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