branch: externals/cpio-mode
commit 7360f6b61f9cbf13445bd2c41c6315f4a0345a5f
Author: dlewan <[email protected]>
Commit: GitHub <[email protected]>
Paring down to the bare application.
---
QUESTIONS | 64 ---------------------------------------------------------------
1 file changed, 64 deletions(-)
diff --git a/QUESTIONS b/QUESTIONS
deleted file mode 100644
index 9029cce..0000000
--- a/QUESTIONS
+++ /dev/null
@@ -1,64 +0,0 @@
-# -*- coding: utf-8 -*-
-# $Id: QUESTIONS,v 1.7 2019/01/07 05:27:52 doug Exp $
-
-#
-# Copyright © 2019 Free Software Foundation, Inc.
-# All rights reserved.
-#
-# This program is free software: you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation, either version 3 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program. If not, see <http://www.gnu.org/licenses/>.
-#
-
-cpio(1) related questions:
-• cpio(1) accepts block size on its command line.
- How should that be handled?
- One obvious choice is via customization,
- but that still feels long term.
- What would be other ways?
-• Similarly, what about --swap-bytes and --swap-halfwords?
-• How should --link be implemented?
-• And --[no-]-absolute-filenames?
- This might be reasonable to customize.
-• How about --dereference?
-• Does --owner=[USER][:.][GROUP] make sense for anyone besides root?
- Similarly for --no-preserve-owner.
-• The extract functions act like --preserve-modification-time is set by
default.
- Is that the right thing.
-• The function of --unconditional has an implicit implementation in cpio-mode.
- Via cpio-dired cpio-mode tries to act like dired and allow over-writing
- after an affirmative response to a prompt.
- From lisp code, however, it will over-write any files.
- Is that the right way to operate?
-• How should I handle (1) contiguous data files, (2) doors (on Solaris)
- and (3) migrated files (Cray)?
-
-Dired related questions:
-• I only use Linux and other UNIX flavored operating systems.
- M-x dired-clean-directory "flags numerical backups."
- What do numerical backups look like?
-• How should I interpret M-x cpio-dired-find-alternate-entry?
- M-x cpio-dired-flag-backup-entries?
- M-x cpio-dired-hide-all?
- M-x cpio-dired-hide-subdir?
-• The following commands prepare things for shell commands.
- How should I interpret them?
- M-x cpio-dired-mark-entries-containing-regexp
-• Should renaming marked files unmark them?
- For example, moving them to a directory.
- They currently remain marked.
-• How should I handle undo?
- Can you undo an entry's deletion?
- chown, etc.?
-• Should killing the archive also kill its entry contents buffers?
-
-Package related:
