For additional details see the SVNBook: “Status of working copy files and directories”. The common statuses: U: Working file was updated G: Changes on the repo were automatically merged into the working copy M: Working copy is modified C: This file conflicts with the version in the repo ?: This file is not under version … Read more
We practice highly componentised development using Java, we have about 250 modules in trunk that have independent life cycles. Dependencies are managed through Maven (that’s a best practice right there), every iteration (bi-weekly) actively developed modules get tagged with a new version. 3 digit version numbers with strict semantics (major.minor.build – major changes means backwards … Read more
Have you ever: Made a change to code, realised it was a mistake and wanted to revert back? Lost code or had a backup that was too old? Had to maintain multiple versions of a product? Wanted to see the difference between two (or more) versions of your code? Wanted to prove that a particular … Read more
If you have access the repository itself (not a working copy), you should be able to dump the current repository, filter it to only include information about the docs folder, and load it into the other repository. Would be something like this: svnadmin dump /svn/old_repos > ./repository.dump svndumpfilter include path/to/docs –drop-empty-revs –renumber-revs –preserve-revprops < ./repository.dump … Read more
If you follow my recommendations below (I have for years), you will be able to: — put each project anywhere in source control, as long as you preserve the structure from the project root directory on down — build each project anywhere on any machine, with minimum risk and minimum preparation — build each project … Read more
Essentially you have to have admin rights (directly or indirectly) to the repository to do this. You can either configure the repository to allow all users to do this, or you can modify the log message directly on the server. See this part of the Subversion FAQ (emphasis mine): Log messages are kept in the … Read more
For full path names of changed files: git log –name-only For full path names and status of changed files: git log –name-status For abbreviated pathnames and a diffstat of changed files: git log –stat There are a lot more options. Check out the documentation.
Edit: Oh well, the question edit was made while I was typing. This is an answer to Is there a way to combine two or more repositories maintaining the version history for both? Assuming that The existing repositories have a structure like: repository root branches tags trunk and you want a structure something like: repository … Read more
In Subversion (and CVS), the repository is first and foremost. In git and mercurial there is not really the concept of a repository in the same way; here changes are the central theme. +1 The hassle in CVS/SVN comes from the fact that these systems do not remember the parenthood of changes. In Git and … Read more
If you want to analyse a local working copy, the best tool is svnversion, which comes with Subversion and produces output like 968:1000M. The documentation says: The version number will be a single number if the working copy is single revision, unmodified, not switched and with an URL that matches the TRAIL_URL argument. If the … Read more