public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jeremy Bopp <jeremy@bopp.net>
To: cygwin@cygwin.com
Subject: Re: Rolling back to 1.6.x Subversion
Date: Thu, 17 Nov 2011 16:33:00 -0000	[thread overview]
Message-ID: <4EC53744.9050205@bopp.net> (raw)
In-Reply-To: <CAEhDDbDJ6_BvfjgFGaUWSduMSLdVJRYNUP6TCutRKCO=4FfuHA@mail.gmail.com>

On 11/17/2011 05:12, Csaba Raduly wrote:
> On 11/17/11, Andy Koppe  wrote:
>> Can one use different svn clients on the same working copy, even if
>> they are the same version? I've always been wary of that due to fear
>> of subtle differences in working copy format. Character encoding and
>> line endings are two possible trouble spots that come to mind.
> 
> I regularly use Cygwin's SVN and Subclipse in a Windows version of
> Eclipse and never had any problems. I had to postpone upgrading to the
> Subversion 1.7 Cygwin package until Subclipse 1.8 came out, which
> supports the 1.7 working copy format.

One of the really smart things that the SVN project has done is insulate
the working copy from most of the horrors of line ending differences.
The administrative files appear to either have a strict line ending
definition for all platforms or (more likely) clients are expected to be
flexible regarding line ending handling within the files.  The use of
the svn:eol-style property on source files allows for a great deal of
flexibility regarding management of line endings within the working copy.

Ultimately, any problems boil down to the text editors in use and not
the various SVN clients.  As far as I can see, only the combination of
setting svn:eol-style to native and using a crummy text editor could
expose unexpected problems when mixing Cygwin and Windows SVN clients
within a single working copy.  Those problems would really only be in
the text editor and not SVN however since the text editor could receive
a file with unsupported line endings if the Cygwin client checked the
file out.  Either SVN client would do the right thing with the file upon
commit regardless of the line endings it ended up having after editing.

There can't be very many users out there mixing both Cygwin and Windows
SVN clients with a text editor that completely chokes on Unix line
endings. :-)  I've been really impressed with how gracefully SVN handles
this whole line ending issue.

-Jeremy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-11-17 16:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 23:06 Jim Garrison
2011-11-17  0:53 ` Jeremy Bopp
2011-11-17  7:50   ` Andrey Repin
2011-11-17 15:37     ` Jeremy Bopp
2011-11-17 16:10       ` Jon Clugston
2011-11-17 16:47         ` Jeremy Bopp
2011-11-17 19:05           ` Andrey Repin
2011-11-17  9:10 ` Andy Koppe
2011-11-17 11:12   ` Csaba Raduly
2011-11-17 16:33     ` Jeremy Bopp [this message]
2011-11-17 19:05   ` Andrey Repin
  -- strict thread matches above, loose matches on Subject: below --
2011-11-15 21:47 Sean LeBlanc
2011-11-16 15:18 ` Jeremy Bopp
2011-11-16 21:16   ` David Rothenberger
2011-11-16 22:35   ` Andrey Repin
2011-11-16 23:01     ` David Rothenberger
2011-11-17 19:06     ` Warren Young
2011-11-17 22:50       ` Andrey Repin
2011-11-18  0:14         ` Warren Young
2011-11-18  9:50           ` Andrey Repin
2011-11-18 14:25           ` Csaba Raduly
2011-11-18 17:23             ` Dave Korn
2011-11-19  9:30             ` Warren Young

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EC53744.9050205@bopp.net \
    --to=jeremy@bopp.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).