working-copy

问题 I cannot do a SVN commit. I get this error: org.apache.subversion.javahl.ClientException: The working copy needs to be upgraded svn: Working copy 'C:\.... is too old (format 10, created by Subversion 1.6) How can it be fixed? 回答1: You have to upgrade your subversion client to at least 1.7. With the command line client, you have to manually upgrade your working copy format by issuing the command svn upgrade : Upgrading the Working Copy Subversion 1.7 introduces substantial changes to the

问题 I cannot do a SVN commit. I get this error: org.apache.subversion.javahl.ClientException: The working copy needs to be upgraded svn: Working copy 'C:\.... is too old (format 10, created by Subversion 1.6) How can it be fixed? 回答1: You have to upgrade your subversion client to at least 1.7. With the command line client, you have to manually upgrade your working copy format by issuing the command svn upgrade : Upgrading the Working Copy Subversion 1.7 introduces substantial changes to the

问题 I have PHPStorm installed and i open a directory containing a PHP project with SVN. Under the SVN tab in the Changes i encounter the following error: Error updating changes: svn: E155021: The client is too old to work with the working copy at "..." (format 31). Some ideas? I have TortoiseSVN 1.7.7 installed, when i open the project the first time everything worked great, but on further opening the above error appear. 回答1: Working copy format has changed in Subversion 1.8, so after upgrading

问题 I work on my school projects on two machines- my laptop and desktop. Recently I've started using subclipse for version control, and have it plugged in Eclipse on both machines. While working on a single machine, I understand the checkout/commit process and synchronizing in the Team Synchronizing tab. So, how do I update the working copy of the other machine in subclipse without having to checkout and overwrite the entire project on the local machine? 回答1: Right click on the project and select

问题 I work on my school projects on two machines- my laptop and desktop. Recently I've started using subclipse for version control, and have it plugged in Eclipse on both machines. While working on a single machine, I understand the checkout/commit process and synchronizing in the Team Synchronizing tab. So, how do I update the working copy of the other machine in subclipse without having to checkout and overwrite the entire project on the local machine? 回答1: Right click on the project and select

问题 We have a very complex SVN tree at my employer that has several project trees contained within the same repository, as follows (each leaf in this diagram has a complete trunk/branches/tags structure in it, btw) svn.contoso.com/root_repository_path/ |- project1 |- project2 | |- subprojectA | |- subprojectB |- project3 |- project4 |- |- subprojectA |- |- subprojectB |- project5 (the project I'm on) This works fine so far. However, a fellow developer did a bit of reorganizing, and moved project5

问题 i wonder where gitosis stores the working copies of my repositories. I can see the filetree with the gitweb interface but cant find any working copy in /srv/gitosis/repositories/testrepo. Iam also able to push and clone to the repo. But how can i manage to write my deploy-script without knowing the path of the working copy? 回答1: gitosis stores repositories bare, that is, without a working directory at all. You will have to clone /srv/gitosis/repositories/testrepo somewhere else for deployment

问题 How do I do this in Subclipse: svn rm --keep-local file 回答1: This option is not exposed in Subclipse. So you have to stash the file somewhere and then delete it and commit it and put it back locally. 来源： https://stackoverflow.com/questions/8062428/remove-file-from-repository-without-deleting-local-copy

问题 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

问题 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