Hi, Von: Daniel Shahaf [mailto:danie...@elego.de]
> David Schweikert wrote on Thu, Jul 04, 2013 at 15:04:34 +0200: > > I was thinking that we could use something like a "svn update > > --readonly", where svn doesn't any check anything on the working copy, > > but just applies any changes committed since the last update. > > That's a common scenario, for example it applies to: > > http://subversion.apache.org/faq.html#website-auto-update > https://svn.apache.org/repos/asf/subversion/trunk/tools/server- > side/svnpubsub/svnwcsub.py > > so enhnacing the core to support it better is not a bad idea.[1] I'm not > sure whether specifically svn update --do-not-crawl-the-disk is the best way > forward; Johan's suggestion of a broader users@ discussion might lead to > identifying a better solution. Is it really always crawling the whole working copy? It could do so later, and just for the nodes which were actually touched by the update. > [1] Disclaimer: y $OTHERWORK uses svnwcsub to manage >15GB of live web sites > (with wc's on local disk), so I have an interest here. Best regards Markus Schaber CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH Inspiring Automation Solutions 3S-Smart Software Solutions GmbH Dipl.-Inf. Markus Schaber | Product Development Core Technology Memminger Str. 151 | 87439 Kempten | Germany Tel. +49-831-54031-979 | Fax +49-831-54031-50 E-Mail: m.scha...@codesys.com | Web: http://www.codesys.com | CODESYS store: http://store.codesys.com CODESYS forum: http://forum.codesys.com Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
