Laird Nelson wrote:
> Laine Stump wrote:
> > I have files with spaces in them (not by choice - InstallShield saves
> > some project info in files containing spaces in the names), and the only
> > trouble I've had is spurious messages when doing cvs update from a
> > parent directory of the directory containing the "spacey file". add,
> > checkout, and commit work just fine (from the cvs commandline, at
> > least).
>
> The place where there is LOTS of trouble (not insurmountable, but close)
> is in the whole {commit,log}info/verifymsg mechanism. If you don't run
> any scripts off the back of your cvs installation, you're right; as long
> as you quote things stuff generally works.
We have a version of log_accum.pl that seems to work well with filenames with
spaces -- except the automatic status doesn't work if more than one file is
commited in one directory. We didn't even try to fix this problem since we
don't use this option, so I can't say how hard it will be to fix this.
I can mail this script (private or to the list) if someone wants it. It adds
newsposting and HTML output (using CSS) to the version found in the
distribution.
Peter
