Laine Stump <[EMAIL PROTECTED]> 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).
> I'm using 1.10.8, but I believe it was working this way with 1.10 as
> well.
>> Larry Jones <[EMAIL PROTECTED]> wrote:
>> > No. Most of the core of CVS handles spaces in filenames correctly, but
>> > there are lots of little bits and pieces that don't and so far none of
>> > the developers has been sufficiently motivated to track them all down
>> > and fix them.
> Gerhard Ahuis writes:
>> What about the cvs checkout part ? Because this is the reason why cvsweb
>> cannot download filenames with spaces from the repository. Is there a
>> way to get around this problem..?
> Are you sure the problem isn't with cvsweb?
There is even a big comment in cvsweb that cvs is buggy with spaces in
filenames. cvsweb is doing cvs checkout "first_part second_part" and cvs
always interpret this as two files what ever quoting characters are used.
Gerhard.
--
Gerhard Ahuis JO32GL It's good to be independent
[EMAIL PROTECTED] ---,--- MHz Linux the Ultimate HAM OS
Unsolicited advertisements subject to $1000 consulting fee.
