Re: commitlog

[Mark D. Baushke]

Brian Murphy <brian@murphy.dk> writes:

> >I have not really thought thru the implications of such a change, but it
> >would be useful to be able to handle all of the possible Unicode
> >characters that some filesystems are starting to use in filenames under
> >some operating systems.
> >
> I think this is a bit ambitious - try seeing what happens when you run
> "cvs up"
> in a directory with a filename containing carriage returns:
> 
> from bash:
> $ touch $'a\nb'
> $ cvs up
> ? a
> unrecognized request `b'
> 
> Spaces on the other hand are reasonably easy to handle in that they
> already work except for problems quoting when external programs are
> called.

Granted. However, choosing a solution that only addresses space
characters in filenames when there would appear to be a more general
problem to solve seems short-sighted. If we are going to move to a
quoting mechanism, we should consider how to encode the various CVS/*
book-keeping files as well to be able to represent such files as well
as determine a way to get such files into command-line arguments.

        -- Mark