Re: svn client under cygwin

Yanghui Bian wrote:
> The client for windows works ok under cygwin. And I don't know whether there
> are any other benefit to make it built on cygwin.
>
> But such inconsistence does indicate something in the code, I think.

Something in the code, yes, but not necessarily a problem in the code. I think this is the explanation:

When you type "svn status", Subversion generates the pathnames using the separator that is most appropriate for the OS for which it is built, thus using a backslash because it was built for Windows.

When you type "svn add */*", the Bash shell expands the command line to (something like) "svn add cfg/httpd.conf cfg/.bashrc" and then Subversion's warning message just repeats the string that it was given, thus using a normal (forward) slash.

- Julian

>>Yanghui Bian wrote:
>>>
>>>I run svn client under Cygwin. The confusing thing is that svn output
>>>has different path separators.
>>>
>>>$ svn status
>>>M cfg\.bashrc
>>>M cfg\lisp\init_emacs.el
>>>$ svn add */*
>>>svn: warning: 'cfg/httpd.conf' is already under revision control
>>>svn: warning: 'cfg/.bashrc' is already under revision control
>>>
>>>In svn status , it uses \ while in svn add, it uses /.
>>>
>>>Are there any possibilities to make them consistent? Under Cygwin, "/"
>>>is preferred. Thank you.
>>
>>Yes, build the client with cygwin instead of using the Win32 binary in a
>>cygwin environment.
>>
>>--
>>Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 11 04:04:30 2003