version-control

问题 I have no idea, which files should be versioned for a new android project created in eclipse. Could anyone tell me, what I should add?? 回答1: Pretty much everything you need to build your project, including: .project and .classpath (yes, you should definitively add them, provided the .classpath doesn't include any absolute path: any other Eclipse users who would access your versioned project will thank you for that) .settings content (for project Eclipse specific settings) other build-related

问题 I have been maintaining the git mirror of the watir project. Some time a couple weeks ago, we had someone ready to submit their first git-based patch. Unfortunately, we ran into some issues regarding line endings (CRLF vs. LF, etc.) because of the multi-platform nature of the project. I tried what I could to set the autocrlf option (to 'input'), and do some --hard resets. However, a few days later, the daily update (git svn rebase) is spewing this error: Incomplete data: Delta source ended

问题 We're a distributed team of 5 developers working on rather large integrations project. We currently use SourceSafe (yes I know it sucks but it has just worked until recently and we've used it forever). Our biggest problem has recently become performance. Checking in and out project just takes forever and we're finding ourselves spending a lot of time just waiting for SourceSafe (yes we've turned off anti-virus check and all the other performance boost trix - it's still slow). We're now

问题 Our project is a content management system supporting several dozen of our websites. The development group started off small and in one location, and we dealt with a fairly standard coding/deployment strategy. We coded off of trunk and insisted on a clean trunk. Every few days we would tag trunk and deploy to the test server. If all worked out, we'd deploy to Production and move on. That worked well for a while until the team grew. We frequently faced situations where the revision that was

问题 In the spirit of keeping my SVN trunk clean and ready for deployment, I've been utilizing the following source control model. For the impatient, the basic concept is that you create development branches to do actual development, and leave the trunk clean and ready for deployment, at any time (no junk in the trunk). In addition to this, I am configuring TeamCity for continuous integration. Within TeamCity, I'd like to ensure that all development branches, as well as the deployment-ready branch

问题 I'm not sure what I did to cause this, but adding a new file or package in IntelliJ now doesn't add them to subversion, and I have to add them manually via right-click -> subverion -> add. Is there a setting that controls this behaviour? 回答1: Go to File -> Settings -> Version control -> Confirmation -> When files are created You're probably looking for " Add silently ". Note: In IntelliJ 6 or earlier versions this is done with File -> Settings -> Version control -> General Settings -> Add

问题 Say I have a website and a database of that website hosted locally on my computer (for development) and another database hosted (for production)...ie first I do the changes on the dev db and then I do the changes to the prod DB. What is the best way to transfer the changes that I did on the local database to the hosted database? If it matters, I am using MS Sql Server (2008) 回答1: The correct way to do this with Visual Studio and SQL Server is to add a Database Project to the web app solution.

问题 I would be interested to in knowing how you out there handle the bumping the version number for new releases issue. How do you handle the version number in associated files like man pages, etc. The software is build with the gnu tool chain so autoconf, automake, etc are available and used for the version number of the application. So that information can be reused. git is used as a vcs. One possibility would be introduce an extra, new target in Makefile.am that does a sed/awk to replace

问题 I am a novice in the world of source/version control and I have been doing as much reading as physically possible to get my head around the different techniques that people use for their own source/version control. One thing that I have noticed is a pretty distinct break in the methods of developers into two (possibly more?) groups: one group prefers to keep their trunk in an always-stable state and performs all maintenance and future development in the branches, while others prefer to do all

问题 Is there a way to configure Mercurial to allow for empty commit messages? If you try hg commit through the CLI without entering a commit message, the commit is canceled with: abort: empty commit message . Now, I know that committing without a message is usually considered bad form, but does Mercurial allow it at all? 回答1: You can use just a space, but I'd really discourage it: hg commit -m " " 回答2: If the problem is that you don't want to enter the -m "blah" part you can always set up an