[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] updatedb: the order of file name is changed, but still unspecifi
[PATCH] updatedb: the order of file name is changed, but still unspecified.
Sun, 10 Jan 2016 16:58:02 +0000
* locate/updatedb.sh: fix typo in comment pointed out by Bernhard
* NEWS: point out that the order of file names in the locate
database is now different, but still unspecified.
NEWS | 5 +++++
locate/updatedb.sh | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 8865b8e..f206365 100644
@@ -9,6 +9,11 @@ that character encoding issues are now not likely to cause
fail. It also honours the TMPDIR environment variable if that was
set, and no longer sorts file names case-insensitively.
+The (unspecified) order in which filenames are stored in the locate
+database is now different to previous versions. However, you should
+not rely on locate's output appearing in any particular order in any
Updated translations: Hungarian, Slovak, Dutch, German.
diff --git a/locate/updatedb.sh b/locate/updatedb.sh
index 3861915..3fa01ae 100644
@@ -35,7 +35,7 @@ Written by Eric B. Decker, James Youngman, and Kevin Dalley.
# mechanism to enforce any constraint that the basename of a
# subdirectory has the same character encoding as the basename of its
# parent). The practical effect is that, depending on the way a
-# oarticular system is configured and the content of its filesystem,
+# particular system is configured and the content of its filesystem,
# passing all the file names in the system through "sort" may generate
# character encoding errors in text-based tools like "sort". To avoid
# this, we set LC_ALL=C. This will, presumably, not work perfectly on