We got an entry into the WinCvs Bugzilla about entering CVSROOT:
 
>>>>
Setup: WinCVS in a client/server model using pserver.

If you have a trailing space in the dialog box for the CVSROOT,
the system will not allow the user to log on. 

The WinCVS program should trim unnecessary white space on the CVSROOT variable
before sending to to the server.
<<<<
 
I am not quite sure if that's a bug. IMHO GUI (WinCvs) should not be "too smart" in that case - we don't know what characters are legal for CVSROOT on the server side. Let CVS resolve the error if error happens.
 
However I agree that some indication would be helpfull when the login fails because of white spaces. Thus at the moment I think the following:
1. Give the warning when entering the CVSROOT.
2. Display CVSROOT at the login time in the brackets so the white spaces would be visible. like this(see the spaces!):

cvs login

(Logging in to [EMAIL PROTECTED]:/cvsroot   )

cvs login: authorization failed: server devnet.3d.com rejected access

*****CVS exited normally with code 1*****

3. Assume that 'user is always right' and don't do anything.

4. Really trim white spaces, and maybe other special characters (like '*' or '?').

5. ???
 
I would like to know your opinion on that topic: To trim or not to trim?
 
BR,
Jerzy
 
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.

Reply via email to