Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
several changes included, unfortunately with old indent (happy to see you switching to 4-spaces).
I don't know is use-case for -c is clear (I'm trying to make an example for man-page, I not commited yet though). I have a script similar to join-duplicates.sh (in perl) but using this -c mode - before I had problems with case with two (or more) groups or hardlinks, eg. 5 file entries, all the same content, hardlinked in groups like:
inode / name:
100 / a.txt
100 / b.txt
200 / c.txt
200 / d.txt
200 / e.txt
and with -p mode duff reported duplicate group of
a.txt
c.txt
100 / a.txt
100 / b.txt
100 / c.txt
200 / d.txt
200 / e.txt
in next run it was not impossible to get from duff -p following list:
d.txt
a.txt
and after merge I had
200 / a.txt
100 / b.txt
100 / c.txt
200 / d.txt
200 / e.txt
and so on... never ending story.
Alternatively I could run duff without -p but it causes reporting all the properly hardlinked groups - not fun either. So -c fixes the case :)
I'll try to update the man page during weekend. Feel free to ask about the changes I made - I'd love to see them in duff ;)