From de754902da93e0dbfb9a4954fa0eeb8ee7359e7d Mon Sep 17 00:00:00 2001 From: Sergey Poznyakoff Date: Tue, 27 Jun 2006 13:39:20 +0000 Subject: [PATCH] Update --- doc/sparse.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/sparse.texi b/doc/sparse.texi index 1194357..14a6ea4 100644 --- a/doc/sparse.texi +++ b/doc/sparse.texi @@ -175,8 +175,9 @@ The real name of the sparse file is stored in the variable @code{GNU.sparse.name}. Thus, those @command{tar} implementations that are not aware of GNU extensions will at least extract the files into separate directories, giving the user a possibility to expand it -afterwards @FIXME-ref{how to extract sparse file using third-party -@command{tar}s}. +afterwards. @xref{extracting sparse v.0.x, Extraction of sparse +members in v.0.1 format}, for the detailed description of how to +restore such members using non-GNU @command{tar}s. The resulting @code{GNU.sparse.map} string can be @emph{very} long. Although POSIX does not impose any limit on the length of a @code{x} -- 2.45.2