John Macdonald wrote:
>
> Tony Hoyle wrote :
> || I thought of changing loginfo parameters so they are comma separated... then you
>have the same problem, but with commas instead
> || of spaces (although commas are far less common in filenames than spaces).
>
> A trailing ",v" on filenames is ubiquitous in CVS repositories. That
> might not actually cause problems since CVS commands always deal with
> the original name instead of the RCS name, but it is at least one
> place where commas are far more common than spaces in filenames.
>
OK, but the users normally never see this.
I stuck in a patch that escapes space (and, for good measure, '\') before it sends it
to the scripts. That made it possible
to write scripts that worked. However I'm a bit worried about the internal workings
of CVS relying on there being no spaces.
In the Win32 world spaces are very common, since you very rarely use the command line
to type filenames. We have pre-existing
projects with filenames in it that are almost complete sentences...
Tony
--
[EMAIL PROTECTED]
