branch: externals/truename-cache
commit b72b0db3506584ec274db438795a66c13c4e20b6
Author: Martin Edström <[email protected]>
Commit: Martin Edström <[email protected]>
Doc
---
README.org | 4 +++-
truename-cache.texi | 5 ++++-
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/README.org b/README.org
index 778911b4e7..056d1b76ad 100644
--- a/README.org
+++ b/README.org
@@ -88,7 +88,9 @@ I've not tried that. However, the truename-based method
brings some upsides.
1. It's more hacker-friendly: when something needs debugging, better to see a
file name than some meaningless inode number.
-2. Once you have a list of true names, it is very easy to manipulate.
+2. With inodes, you must make an arbitrary choice of which of any two
duplicates to keep as "canonical".
+
+3. Once you have a list of true names, it is easy to sort, filter and
manipulate correctly.
The assumption that they are true leads to other safe assumptions, such as
that an alphabetic sort automatically groups by directory.
diff --git a/truename-cache.texi b/truename-cache.texi
index f889cf3393..5fdc26d30c 100644
--- a/truename-cache.texi
+++ b/truename-cache.texi
@@ -137,7 +137,10 @@ I've not tried that. However@comma{} the truename-based
method brings some upsi
It's more hacker-friendly: when something needs debugging@comma{} better to
see a file name than some meaningless inode number.
@item
-Once you have a list of true names@comma{} it is very easy to manipulate.
+With inodes@comma{} you must make an arbitrary choice of which of any two
duplicates to keep as "canonical".
+
+@item
+Once you have a list of true names@comma{} it is easy to sort@comma{} filter
and manipulate correctly.
The assumption that they are true leads to other safe assumptions@comma{} such
as that an alphabetic sort automatically groups by directory.
