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

Re: converting from SVN to CVS

From: JeremyP <jeremyp_at_jeremyp.net>
Date: Thu, 29 Jan 2009 14:02:46 +0000

On 29 Jan 2009, at 08:42, Spiro Trikaliotis wrote:

> Hello,
> Erik Huelsmann wrote:
>> Cygwin is an ugly
>> workaround for problems people are having with their OS.
> Oh, that's the problem: We don't like Windows, thus, we don't like
> Cygwin, either. Yes, that's easy.

Actually, that's not what he's saying, in fact quite the opposite.
The Subversion developers fully embrace Windows which is why they have
a native Windows build that doesn't need Cygwin. Cygwin is an ugly
hack to make Windows appear like Unix both at the API and user
interface level.

The issue arises from the fact that Cygwin tools use LF for text file
end of lines, but Windows tools use CR LF. Thus, if you mix Windows
and Cygwin tools you get into a terrible mess. I used to work in a
company that did just that until we realised what was happening and
our source files ended up in a hopeless mess of orphaned CRs and
extraneous blank lines. I'd like to blame Subversion for that, but
unfortunately, we were a CVS shop at the time.

> If the native SVN would work flawlessly on Cygwin (in a bash shell), I
> would use it. In fact, on one machine, I had tested this. However,
> there
> are problems in this setup, too. For example, SVN cannot call
> (Cygwin's)
> vim in a way that I can enter anything into it for commits, and I do
> not
> like calling svn commit --file XXX to do a commit.

You should try TortoiseSVN. Then the editor becomes irrelevant.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-29 15:03:53 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.