On Thu, Nov 29, 2012 at 9:19 AM, Dominik Psenner <[email protected]> wrote:
> That inconsistent line ending seems to be a problem with the
> eol-style:native on my tortoisesvn client versioned as:
>
> TortoiseSVN 1.7.10
> Subversion 1.7.7
>
> That svn client kept modifying half of all EOL in the files to windows
> format and the other half to unix format while preparing to send the file
> contents. I had to manually go through all files and convert all EOL to unix
> style until the commit went through. Pretty annoying, but doable.

Ouch.

After a long time using OSX only, I often wonder how developers can
still work with Windows.
That said, the recent OSX developments make me sad too. Anyway, so far
I am glad that my *nix based system is not so weird when it comes to
line endings.

BTW, there are perl oneliners out there which would have helped you

> The website is now fresh new and up to date. Thanks for your help Christian!
> If we get the chance I would definitely drink a couple of beers together.
>
> :-)
>

Definitely! Maybe next ApacheCon EU?

Cheers
Christian


> Cheers,
> Dominik
>
>>-----Original Message-----
>>From: Christian Grobmeier [mailto:[email protected]]
>>Sent: Wednesday, November 28, 2012 11:02 PM
>>To: Log4NET Dev
>>Subject: Re: FW: Add new FAQ entry
>>
>>> I got that one working too now. It was because I mixed mvn3 files with
>>the
>>> ones I generated with mvn2. But now the commit fails with:
>>>
>>> Error: Commit failed (details follow):
>>> Error: Changing file
>>> Error:  '\log4net-site-content\log4net\log4net-1.2.11\project-
>>reports.html'
>>>
>>> Error:  is forbidden by the server
>>> Error: Access to
>>> Error:
>>> '/repos/infra/!svn/txr/839889-
>>i0ux/websites/production/loggingtest/content/l
>>> og4net/log4net-1.2.11/project-reports.html'
>>> Error:  forbidden
>>>
>>> I have the impression that this is something someone else has to fix. :-)
>>
>>:-)
>>
>>For some reason i think the link in the wiki is wrong... I found this one:
>>https://svn.apache.org/repos/infra/websites/production/logging/content/
>>
>>it does not containt loggingtest, just logging.
>>
>>Could you try it with that again? At least my browser shows me correct
>>content
>>
>>Cheers
>>Christian
>>
>>
>>> Cheers,
>>> D.
>>>
>>
>>
>>
>>--
>>http://www.grobmeier.de
>>https://www.timeandbill.de
>



--
http://www.grobmeier.de
https://www.timeandbill.de

Reply via email to