X-Git-Url: https://www.fleuret.org/cgi-bin/gitweb/gitweb.cgi?a=blobdiff_plain;f=finddup.1;h=3eec991648422988f2d7b5139bc5ef7145408393;hb=84317c21dc50141fff4a8f1fc1ac3c075e29923f;hp=c86df1ea89daff89f228e2a87944407689e4ebb1;hpb=2e218d38854bc5934f3935bc7aa6eab598770bdb;p=finddup.git

diff --git a/finddup.1 b/finddup.1
index c86df1e..3eec991 100644
--- a/finddup.1
+++ b/finddup.1
@@ -1,4 +1,4 @@
-.TH "FINDDUP" 1 "Mar 2010" "Francois Fleuret" "User Commands"
+.TH "FINDDUP" "1.1" "Mar 2010" "Francois Fleuret" "User Commands"
 
 \" This man page was written by Francois Fleuret <francois@fleuret.org>
 \" and is distributed under a Creative Commons Attribution-Share Alike
@@ -10,12 +10,13 @@ finddup \- Find files common to two directories (or not)
 
 .SH "SYNOPSIS"
 
-\fBfinddup\fP [OPTION]... DIR1 [[and:|not:]DIR2]
+\fBfinddup\fP [OPTION]... [DIR1 [[and:|not:]DIR2]]
 
 .SH "DESCRIPTION"
 
-With a single directory argument, \fBfinddup\fP prints the duplicated
-files found in it.
+With one directory as argument, \fBfinddup\fP prints the duplicated
+files found in it. If no directory is provided, it uses the current
+one as default.
 
 With two directories, it prints either the files common to both DIR1
 and DIR2 or, with the `not:' prefix, the ones present in DIR1 and not
@@ -46,13 +47,16 @@ ignore files and directories starting with a dot
 ignore empty files
 .TP
 \fB-c\fR, \fB--hide-matchings\fR
-do not show which files from DIR2 corresponds to files from DIR1
+do not show which files from DIR2 correspond to files from DIR1
 (hence, show only the files from DIR1 which have an identical twin in
 DIR2)
 .TP
 \fB-g\fR, \fB--no-group-ids\fR
 do not show the file group IDs
 .TP
+\fB-t\fR, \fB--time-sort\fR
+sort files in each group according to the modification times
+.TP
 \fB-p\fR, \fB--show-progress\fR
 show progress information in stderr
 .TP
@@ -71,10 +75,10 @@ file content.
 
 Here are the things I tried, which did not help at all: (1) Computing
 md5s on the whole files, which is not satisfactory because files are
-often never read entirely hence the md5s can not be properly computed,
-(2) computing XOR of the first 4, 16 and 256 bytes with rejection as
-soon as one does not match, (3) reading parts of the files of
-increasing sizes so that rejection could be done with a small fraction
+often not read entirely, hence the md5s can not be properly computed,
+(2) computing XORs of the first 4, 16 and 256 bytes with rejection as
+soon as one does not match, (3) reading files in parts of increasing
+sizes so that rejection could be done with only a small fraction read
 when possible, (4) using mmap instead of open/read.
 
 .SH "WISH LIST"