-2006-05-20 Jim Meyering <jim@meyering.net>
+2006-05-25 Paul Eggert <eggert@cs.ucla.edu>
* Version 6.0-cvs.
+ * NEWS: Remove mention of --seed. We'll replace it with something
+ better, and don't want to indicate that it is supported.
+ * src/sort.c (usage): Likewise.
+
+2006-05-20 Jim Meyering <jim@meyering.net>
+
* src/chmod.c (main): Use FTS_PHYSICAL here, too.
* src/du.c (main): Rename local, s/symlink_deref_bit/symlink_deref_bits/
for every file, but provides almost the same level of protection
against mistakes.
- sort now accepts the --random-sort (-R) option and `R' ordering option,
- as well as the --seed=STRING option.
+ sort now accepts the --random-sort (-R) option and `R' ordering option.
** Bug fixes
+2006-05-25 Paul Eggert <eggert@cs.ucla.edu>
+
+ * coreutils.texi (sort invocation): Remove mention of --seed, since
+ it's going away.
+
2006-05-04 Eric Blake <ebb9@byu.net>
* coreutils.texi (Examples of date): Give example of @seconds.
@cindex random sort
Sort by hashing the input keys and then sorting the hash values. This
is much like a random shuffle of the inputs, except that keys with the
-same value sort together. Normally the hash function is chosen at
-random, but this can be overridden with the @option{--seed} option.
+same value sort together. The hash function is chosen at random.
@end table
reliably handle arbitrary file names (even those containing blanks
or other special characters).
-@item --seed=@var{string}
-@opindex --seed
-@cindex seed for random hash
-Use data from @var{string} to choose the hash function used by the
-@option{--random-sort} option. This option can be used to reproduce
-results of earlier invocations of @command{sort} with
-@option{--random-sort}. However, results are not necessarily
-reproducible across different @command{sort} implementations (e.g.,
-@command{sort} on little-endian versus big-endian architectures, or
-from one version of @command{sort} to the next).
-
@end table
Historical (BSD and System V) implementations of @command{sort} have