Instructions as sent to the FOTW mailing list by Peter Hans van den Muijzenberg
for processing the delete list into a script that can do the removing for you. It is fairly simple;
this is the shell version for unix et alii (but check Instructions for GUI).

Read all this until the end first, make sure you understand what you'll be doing.
While you're at it, note that the '-s (single quotes) are just for readability, you don't
actually use them anywhere.

Open the obsolete files list in a text editor. If you have lists for more than one month,
start with the oldest and go from 1 to 10 for each one in turn.

Immediately save the list under a different name, '<something>.sh', and save it as
text with Unix line-ends. (If your editor doesn't have that option, save however you can, and
compare the exact file sizes ('ls -l') to check that your file is one byte per line smaller.
If it isn't, try starting a new document in the editor, copying all text, and saving that one.
Check again; if still not right, keep at it until you know a solution.). Saving as a new file
also saves you from changing the original file. Sooner or later you will make a mistake. Yes, you too;
we're all human. If so, start at 1 again (or at 0).

You might, however, want to keep the removed obsolete files (especially since this is from the shell,
where removed files are really gone, not just moved to a trash can). To keep the files, you can use
these steps below instead of the steps above with the same number:

If this is the first time you're moving files, write the following line at the top of the list:'mkdir obsolete obsolete/flags obsolete/images obsolete/misc'.
(It won't hurt if you if you do this step again, but the only effect will be to generate
error messages before continuing.)

Doing it this way, you'll move obsolete files to /obsolete/, at the same level as /flags/ etc.,
all neatly in their own subdirectories. Here the obsoleted files will remain until you really remove them,
or until FotW obsoletes a file with the exact same file name.

The above is intended for shell use. Doing the same thing using a GUI depends somewhat on your set-up.
You'll need these steps:

Add as the very first line of the file a text like '#!/bin/sh'.
But if you find step 10 doesn't do anything, try '#!/usr/bin/sh' instead.
And if that doesn't work, try both with different shells instead of sh: bash, csh, bsh, ksh, ... .

Now that you have a copy in the right location, change the file permission
to allow execution - probably: right-click / Properties / Permissions / Executable, or a similar sequence
- and once you've done so, double click. If you're sure it doesn't do anything, and you checked
it wasn't merely too fast to be noticed, go back to step 7 and try a different option.