2012/6/11 Christopher Schultz <ch...@christopherschultz.net>:
> Konstantin,
>
> On 6/7/12 5:49 PM, Konstantin Kolinko wrote:
>> 2012/6/8 Konstantin Kolinko <knst.koli...@gmail.com>:
>>> 2012/6/8 Christopher Schultz <ch...@christopherschultz.net>:
>>>> All,
>>>>
>>>> http://tomcat.apache.org/native-doc/
>>>>
>>>> It says that tcnative 2.0.0 has been released, has no date, and links to
>>>> non-existent files.
>>>>
>>>> Same thing with http://tomcat.apache.org/native-doc/news/2010.html
>>>>
>>>> Can someone take a look?
>>>>
>>>
>>> Apparently it was built from native/trunk, instead of native/branches/1.1.x
>>>
>>
>> Fixed.
>
> Thanks. I noticed when I recently updated the website (security pages),
> svn pulled-in tcnative documentation at the same time.  I don't grok svn
> module resolution but is it possible that it is misconfigured, and that
> I broke the tcnative portion of the docs by running 'svn up' according
> to the documentation?
>

The last change to native-doc was my setting svn:eol-style on some files
http://svn.apache.org/viewvc?view=revision&revision=1347816

I might have forgotten to run "svn up" after that, as this operation
is essentially a noop.

You are not able to break anything by "svn up". What is in svn is
considered the correct version.  You can use "svn st" (status) to
check that there are none locally modified files on the server.

We are going to move to svnpubsub one day and those "svn up"s will
become a history... The only pending question that prevents us from
switching now is with tomcat-taglibs and tomcat-maven websites which
are not in svn.

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to