On Thu, Jan 17, 2013 at 2:58 PM, Bert Huijben wrote:
> A lot of users have SvnKit in their Jenkins installation. Are you sure that
> you aren't mixing a normal svn with some svnkit version?
>
Oh, that is interesting. I will research that.
Best,
Laird
--
http://about.me/lairdnelson
On Thu, Jan 17, 2013 at 2:01 PM, David Chapman wrote:
> Hmm, "only the EOL changed." Do you mean that literally, meaning there
> is only one line in the file? If so, does the original file have a newline
> at the end of the last line? Maybe newline conversion is adding one.
>
Thanks for your
One specific machine. :-(
On Thu, Jan 17, 2013 at 1:56 PM, Andy Levy wrote:
>
>
> On Thu, Jan 17, 2013 at 4:45 PM, Laird Nelson wrote:
>
>> On Thu, Jan 17, 2013 at 1:40 PM, Andy Levy wrote:
>>
>>> Automatic EOL conversions, assuming they're adhering to
On Thu, Jan 17, 2013 at 1:40 PM, Andy Levy wrote:
> Automatic EOL conversions, assuming they're adhering to svn:eol-style,
> should not trigger this.
>
Glad to hear it.
The ecosystem in question is Jenkins running on Windows, which invokes the
command line svn executable (packaged/shipped by Sl
Hello; we're seeing a local modification being reported on a particular
file on a clean checkout. We're using svn 1.7.7.
The file in question has the svn:eol-style property set to native.
What I mean by this:
A fresh checkout happens (svn co ...).
Down comes the whole project. So far so good.
Hello, and thanks, first of all, for a great version control system.
I am seeing a very odd behavior that I hope I can chalk up to pilot error.
One of my developers on Windows 7, running the CollabNet-supported
Subversion 1.6.13 binaries, does this command:
svn diff pom.xml
...in a directory wi
