summaryrefslogtreecommitdiff
path: root/lisp/tar-mode.el
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>1994-04-25 23:34:17 +0000
committerRichard M. Stallman <rms@gnu.org>1994-04-25 23:34:17 +0000
commitce2100661a8ecf6eab543e349382b26b37b3a2e4 (patch)
tree7275a9ce817b02378fa6f71c7c7850f4c071bec1 /lisp/tar-mode.el
parent431e100fd163ec52fd1d27029ce914688e0d191d (diff)
downloademacs-ce2100661a8ecf6eab543e349382b26b37b3a2e4.tar.gz
Comment change.
Diffstat (limited to 'lisp/tar-mode.el')
-rw-r--r--lisp/tar-mode.el14
1 files changed, 14 insertions, 0 deletions
diff --git a/lisp/tar-mode.el b/lisp/tar-mode.el
index b1edbe0375b..962fb60597e 100644
--- a/lisp/tar-mode.el
+++ b/lisp/tar-mode.el
@@ -81,6 +81,20 @@
;;; o Block files, sparse files, continuation files, and the various header
;;; types aren't editable. Actually I don't know that they work at all.
+;;; Rationale:
+
+;;; Why does tar-mode edit the file itself instead of using tar?
+
+;;; That means that you can edit tar files which you don't have room for
+;;; on your local disk.
+
+;;; I don't know about recent features in gnu tar, but old versions of tar
+;;; can't replace a file in the middle of a tar file with a new version.
+;;; Tar-mode can. I don't think tar can do things like chmod the subfiles.
+;;; An implementation which involved unpacking and repacking the file into
+;;; some scratch directory would be very wasteful, and wouldn't be able to
+;;; preserve the file owners.
+
;;; Code:
(defvar tar-anal-blocksize 20