From: Andrey Repin <anrdaemon@freemail.ru>
To: Andy Koppe <andy.koppe@gmail.com>, cygwin@cygwin.com
Subject: Re: Rolling back to 1.6.x Subversion
Date: Thu, 17 Nov 2011 19:05:00 -0000 [thread overview]
Message-ID: <38581395.20111117230209@mtu-net.ru> (raw)
In-Reply-To: <CAHWeT-ZtdYPK77RYXae6hG4WNKJtcO36CEsUUfUz2MRUp2B7uQ@mail.gmail.com>
Greetings, Andy Koppe!
> Can one use different svn clients on the same working copy, even if
> they are the same version?
You can even use them (literally) simultaneously. Subversion introduced an
appropriate locking mechanics to ensure as much as possible that all
transactions are atomic.
But, as you pointed out, they all must be of the same version.
> I've always been wary of that due to fear
> of subtle differences in working copy format.
Working copy format is dictated by the Subversion client layer http://svnbook.red-bean.com/en/1.7/svn.developer.layerlib.html#svn.developer.layerlib.client
not by a program or moon phase.
> Character encoding and line endings are two possible trouble spots that come
> to mind.
Subversion on inside using UTF-8. But this could be a problem when dealing
with files outside Subversion.
> I've certainly seen problems with CVS: Windows CVS clients often
> convert to Windows line endings on checkout, whereas Cygwin CVS
> doesn't, so if you check out with one and then do a 'cvs diff' with
> the other, it says that every line has changed.
This could only happen, if you intentionally set svn:eol-style to "native".
Otherwise, it will preserve line endings, or even convert them to the desired
format upon submission.
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 17.11.2011, <22:52>
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2011-11-17 19:05 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
2011-11-17 19:05 ` Andrey Repin [this message]
-- 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=38581395.20111117230209@mtu-net.ru \
--to=anrdaemon@freemail.ru \
--cc=andy.koppe@gmail.com \
--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).