Why SVN still sucks
Because it still is very intuitive for basic things like reverting a file back to a previous version.
ez-3.5$ svn merge -r 9201:9200 kernel/classes/ezcontentobject.php svn: REPORT request failed on '/svn/nextgen/!svn/vcc/default' svn: Invalid editor anchoring; at least one of the input paths is not a directory and there was no source entry ez-3.5$ svn merge -r9201:9200 http://host/trunk/kernel/classes/ezcontentobject.php svn: REPORT request failed on '/svn/nextgen/!svn/vcc/default' svn: Invalid editor anchoring; at least one of the input paths is not a directory and there was no source entry ez-3.5$ cd kernel/classes ez-3.5/kernel/classes$ svn merge -r9201:9200 http://host/trunk/kernel/classes/ezcontentobject.php U ezcontentobject.php
Comments
Are you being sarcastic?
Not at all, SVN might fix a few CVS annoyances, but it adds a whole lot of them too. This is just one example.
You mean UNintuitive, no?
Right, UNinituitive
Derick's pointing out the fact that you have to live with other issues with svn which are highly annoying but then again cvs also has other annoyances.
SVN tool support in eclipse/windows is poor. Subclipse, subversive and Tortoise all corrupt my repository on a bi-weekly basis. Not the actual source under version control, but the internal meta-info files that SVN keeps. In addition SVN triples the data kept on your local machine resulting in both disk bloat and terribly slow synch times for non-trivial projects.
Worst thing is once corrupted, the "cleanup" command rarely works.
Wait for this to settle down (it's 11/2006 as I write this) before you jump in in a commercial dev envirionment.
Life Line
Merge branch 'xdebug_3_5'
Merged pull request #1111
Disable 'declaration after statement' warning in zend_smart_string.h,…
Specify bicycle parkings covers
Specify street/place names to addresses
Survey housenumbers
Specify whether crosswalks have tactile paving
Specify whether roads have sidewalks
Determine whether ATM allows depositing cash
Survey if places still exist
Survey if places still exist
Specify access to places
Specify whether steps have handrails
Specify width of opening
Specify parking types
Specify whether public transport stops have tactile paving
Survey opening hours
Specify step counts
Survey tactile paving on steps
Specify whether steps have a ramp
Specify which way leads up for steps
Specify path surfaces
Specify whether there are cycleways
Created an entrance
Created a bicycle_parking
Shortlink
This article has a short URL available: https://drck.me/wsss-3fg