svn

问题 I have a rails site. I'd like, on mongrel restart, to write the current svn version into public/version.txt, so that i can then put this into a comment in the page header. The problem is getting the current local version of svn - i'm a little confused. If, for example, i do svn update on a file which hasn't been updated in a while i get "At revision 4571.". However, if i do svn info, i get Path: . URL: http://my.url/trunk Repository Root: http://my.url/lesson_planner Repository UUID: ########

问题 From what I could find around the web, it seems that using git svn is not "persisted". Meaning, if I git svn clone a repository, then push to master and repull a fresh copy in a separate folder, the fresh copy is not aware of svn at all, and cannot be used to synchronize with SVN without reapplication of svn clone . Is there a way around this issue? 回答1: A clone essentially just initializes a new git repository, sets up the origin remote, runs git fetch , and creates a branch based on the

问题 'svn log' shows the log of: 1) files whose content has changed AND/OR 2) files whose properties have changed. Is there a way to show only files for which case 1 applies? 回答1: 'svn log' shows the log of: 1) files whose content has changed AND/OR 2) files whose properties have changed. As you know, svn log's output is organized by commit log messages rather than by files. If you use verbose mode (-v), it will show the files ("paths") associated with each log entry. However some of those paths

问题 When I merge the trunk into a feature-branch, a delete that occurred on the trunk will not be replicated to my working copy. Why will a delete on trunk not delete the same file on a branch when merging? I'm using subversion 1.5 client and server. I'm assuming that changes to the file in the branch will be skipped when reintegrating the branch? What's the best way to redeem the file on trunk, as a colleague deleted the file from trunk only because it was not "ready". Situation: cd project; svn

问题 When I merge the trunk into a feature-branch, a delete that occurred on the trunk will not be replicated to my working copy. Why will a delete on trunk not delete the same file on a branch when merging? I'm using subversion 1.5 client and server. I'm assuming that changes to the file in the branch will be skipped when reintegrating the branch? What's the best way to redeem the file on trunk, as a colleague deleted the file from trunk only because it was not "ready". Situation: cd project; svn

问题 I'm using SVN (TortoiseSVN) and often came into the following situation: I wanted to discard any changes since a specific (old) revision and turn all files back to this specific (old) version. Then I wanted to work further as if this specific (old) revision was the newest one, i.e. I wanted to be able to commit the specific old revision as a new revision. I found several solutions for this problem (for example stackoverflow.com/questions/402159/roll-back-or-revert-entire-svn-repository-to-an

问题 I would like some help in setting up a project in SVN with regards to directory structure. I have read several answers regarding this on SO, but as I am new to this, most of them are difficult to understand. I am building a single library, on which several other distinct project depends on: I need the ability to export MyLibrary (headers and .lib only) easily for use by third parties MyLibrary1 Depends on external libraries, should be able to manage different versions of these libraries!

问题 I have downloaded 64bit Tortoise SVN and installed in C Drive in to my system. I have created seperate folder for SVN client and branch,tags,trunk folders and paste the code and commit in to that SVN server. Studio : next, I tried to set tortoise svn path in to studio Version Control-Subversion-user command line client: path url.. But, I could not find svn.exe in to this path C:\Program Files\TortoiseSVN\bin. Anyway, I could not set path into studio. Exactly dont know, where made mistake ? I

问题 Could anyone give me examples, how I could use diffstat with subversion? I mean, using diffstat to analyze and produce statistics about one or multiple commits. NOTE: Linux commandline examples are OK ;) 回答1: You can simply pipe any diff to diffstat. For example, if you want a stat of the changes made in a specific revision, just retrieve that change from svn and pipe it to diffstat. $ svn diff -r1234:1235 | diffstat You can obviously pipe anything in that svn can create diffs of, which

问题 I'm getting "svn: '.' is not a working copy" when i use the svn log command. I know that i need a working copy for the log command to work but can this be done directly on a repository? My goal is to display the information (change history) of a repository. I think updating the working copy whenever i need the log information is not a good solution. Is there an alternative solution to this or updating a working copy every time i need to log is the only way to go? Thanks in advance. 回答1: Try