4 ms·
* ahem. Revision is always a revision in SVN. It’s rN and all commands accept it. * ahem. All branches in SVN are copies of an existing tree at a particular re
by COMMENT___ 5y ago
* ahem. Revision is always a revision in SVN. It’s rN and all commands accept it.
* ahem. All branches in SVN are copies of an existing tree at a particular revision. Call it a branch or whatever you want. But if you make a copy of your main development tree, you make a branch and you can work on it in the same fashion as if it was git. Merge it back to trunk when done or continue your work and sync with trunk or other branches. The principle is the same.
* Failing “svn up” is an unexpected technical problem that occurs due to problems with the server or network. The problem should never happen in normal cases.
- eru 5y agoTo be honest, Git is pretty good about dealing with 'unexpected technical problems'. It even handles running multiple instances of git commands at the same time rather well.
- hamilyon2 5y agoFirst point: Here is an official svn doc with lots of mentioning of @revision https://edoras.sdsu.edu/doc/svn-book-html-chunk/svn.ref.svn.c.diff.html https://edoras.sdsu.edu/doc/svn-book-html-chunk/svn.ref.svn.... Two styles of revisions is super confusing to users like me. Git confuses me a bit, but not in command syntax. Hope this illustration helps to see what I mean.
- COMMENT___ 5y agoMaybe a more up to date version of the doc will help: https://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html https://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs...