Have your build process call the svnversion command, and embed its output into generated {source|binaries}. This will not only give the current revision (as many other examples here do), but its output string will also tell whether a build is being done in a mixed tree or a tree which doesn’t exactly match the revision … Read more
As Nathan said, cleaning up those files (un-tracking them) is the smart move. But if you must ignore tracked files (which is not the native Git way when it comes to ignoring files: Git only ignores non-tracked files), you can setup a process copying the content of files you want to ignore, and restoring on … Read more
The following are all the supported hooks in Subversion 1.5, from the Version Control with Subversion book: start-commit pre-commit post-commit pre-revprop-change post-revprop-change pre-lock post-lock pre-unlock post-unlock There is no pre-checkout or pre-update hook like you describe.
For one thing, the way that SVN calculates the differences to apply is different between the two methods. Normally, when you apply a range of revisions X to Y from a trunk to the branch in cherry-picking fashion, for example, SVN calculates the differences between the revisions of X to Y in the trunk, and … Read more
Try to add the following configuration directives to your Apache configuration file: LimitXMLRequestBody 8000000 LimitRequestBody 0
Because Subversion’s repository format is entirely internal, they are free to change the representation from one revision to the next. I believe the current revision generally stores reverse deltas (your option 2), but also stores complete snapshots periodically so it doesn’t have to resolve 1000 diffs before returning a result. The Subversion 1.6 release notes … Read more
Two ways: Embed $Id$ or $Revision$ within the code. Then set svn:keywords=”Id Revision” property on the file. This will give you the last modified revision of that source file. Good for smaller projects and scripts. Alternatively, use a Makefile driven process and the command line tool svnversion. (Language specific – this should work for C/C++) … Read more
Tortoise SVN 1.8 now supports this with it’s “Restore after commit” feature. This allow you to make edits to a file, with all of the edits being undone after the commit Per the documentation: To commit only the parts of the file that relate to one specific issue: in the commit dialog, right-click on file, … Read more
After you install Tortoise (separate SVN client not required), create a new empty folder for the project somewhere and right click it in Windows. There should be an option for SVN Checkout. Choosing that option will open a dialog box. Paste the URL you posted above in the first textbox of that dialog box and … Read more
Sounds like you’re using the pre-1.5 merge style and trying to reintegrate the branch into trunk. In that case, what you want to do is first ensure all the trunk changes have been merged in to the branch, and then instead of range-merging the branch to a working copy that points to the trunk, you … Read more