[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r8285 - in trunk/doc/book: . book

From: Jostein Chr. Andersen <jostein_at_josander.net>
Date: 2004-01-14 07:56:59 CET

On Wednesday 14 January 2004 02.55, Garrett Rooney wrote:
> > +
> > + <para>Not to fear, Microsoft Windows users can download a
> > + pre-compiled Windows native Subversion command-line client
> > that + works in the Command Prompt application. Many examples
> > of the + client will work in the Command Prompt, but you may
> > have more + success if you run the examples inside the Cygwin
> > Unix emulation + environment.</para>
> Given the number of issues people have brought up on the mailing lists
> in the past that have been the result of strange interaction between
> cygwin and regular win32 apps like svn, should we really be
> recommending people use cygwin?

Given that Cygwin are used by a very small (but enthusiastic) group of
people and that Subversion are supposed to run natively under a OS: -I
would say no, we should not support it.
If someone can help when someone are in trouble or send patches in order
to fix it, then fine. But I think a lot of things should have priority
over this issue.

As a Linux user, I appreciate the power of the Bash shell, but Cygwin is
not a Windows environment. And after Subversion 1.0 (or 1.1) the number
of native windows users (the Windows console) will get even bigger
related to the Cygwin shell. TortoiseSVN will probably be king anyway.

I have no problem at all to understand why someone prefear to use the
Cygwin shell over the Windows console, but have someone tested Msys
instead of Cygwin when using Subversion on Windows?


http://www.josander.net/kontakt/ ||
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 14 07:59:59 2004

This is an archived mail posted to the Subversion Dev mailing list.