version-control

问题 When you place a Rails project under version control, do you exclude anything? Log files, for example? 回答1: DHH just posted on Twitter that there will be a default .gitignore in Rails 3, which includes: db/*.sqlite3 log/*.log tmp/**/* Which is usually what I exclude, some people also like to exclude the database.yml file if it's going on a public repo and you don't want to expose your database passwords. 回答2: In addition, to what Dan and Sohan suggest, I also ignore any native extensions for

问题 In our project we have several production databases and many devs. Each production database represents some "sub-project/localization version". We use SQL Server 2008. So, I need to develop database versioning strategy using MS Visual Studio Database Project. I have read a lot of articles about database versioning and database projects, but I still have a lot of questions: How developers should implement theirs changes to db project? (Best practice) How to generate the 100% workable "latest

问题 I am working on a Project that is bind in TFS, this project gives me a folder Log. When I execute my project and do some testing it generates text files and store in Log folder. After that when I try to check in files those files are checked in as a new file in TFS. I want TFS to exclude these files. Folders where I store temp files are: \WebPages\ErrorLogs \WebPages\TempReports Is there a setting in TFS where I can say it not to include this folder in TFS but Get latest from server if any?

问题 I am building a wiki-like website, and am wondering how to implement the file versioning to create articles history. I would like to be able, when someone edits a file, to be able to display which parts were edited, and to revert back to a previous file if necessary. EDIT: Thank you for your responses. I started to go through them, and then I realized my post was not very precise. So I may add that I am using Java as a development language (Groovy through Grails to be precise). Also, the

问题 What is the decision tree to know when to split a suite of related and/or cohesive applications into git repo's and/or branches? Should I keep each app in a repo? Or all app's & dependencies in a single repo? Or something in-between? answer How should I organize multiple related applications using git? claims that a repository per project is appropriate, but does not give clues as to what a project would be. And then there's the question of dev, test, integration test, and production

问题 I'm looking for tools and recommendations on how to manage binaries artifacts which together make up a release version. The project looks like this: + Package-Version |__ Component A-Version |__ Component B-Version |__ Component C-Version More levels may exist, such that the components themselves are built from sub-components with their own versions. Currently, we use an Excel with links to the binaries. I hope to improve this by introducing some simple tools that may manage it better. It

问题 I am not able to setup SVN in X-Code 5. Iv tried these steps: 1) Goto-Xcode-Preferences-Accounts-Add Repositories (clicking "+" sign). 2) Enter the url path of the project https://ipaddress:8578/svn/comapny_name/projectname/iphone/ 3)Enter the credentials. At this point of time i get this error message Xcode has modified the URL. Xcode repository accounts represent the root of the repository. Subpaths can be checked out from the checkout window. the Repository was added successfully with the

问题 What are commit messages for? I've always been writing them as an explanation of what I did, but I've recently gotten into a discussion about it with a colleague who writes commit messages explaining why he did. Which one is right, or is there another answer entirely? NOTE: I have absolutely no idea if there is a "right" answer for this. As such, I've labeled it community wiki and will not accept an answer. Upvotes shall decide the winner :) 回答1: As a personal preference, I can tell what was

问题 What would be the ideal location (directory) to check in Third Party Reference Dll's for a .NET Project in a version control system. Typically i have seen most people to put them under bin, so that the runtime can automatically pickup these files. However is that the right way to go. I originally wanted to have a separate directory which is parallel to bin called lib which will contain all third party Dll's , but this needs changes to the applications config file so that the lib directory is

问题 We have pool of MSVS solutions (Solution "A", "B", "C", ... ) that share basic functionality in assembly called "Common.dll". There are 3-5 active solutions (that are under developing) while others are passive and hardly ever be rebuilt. Common.dll is always under developing. There are several options how to keep my solutions code, what will you suggest and why? A). Put common.dll source code to every solution . Pros: it will help active solutions to grow with common.dll side-by-side while