version-control

问题 Having a regular size-efficient backup for only the modified checkedout elements in all views would be a great thing for us, since a great deal of the defined dynamic/snapshot views cannot be included in the daily backup policy. The following ksh code is near to what we would need for a dynamic view, but it trivially assumes that the first line in the config-spec file for the view always selects the checked-out element first ( *element * CHECKEDOUT* ). It will not work well in general. For

问题 I'm new to mercurial (and SCM in general) and I'm stuck at handling a parent child relationship between my two projects. One project is the parent project and is a subset of the other project (or rather, the other one is a superset of the first). I want to work on the two projects in a single local repository as if they were one but I want to publish them to two different public repositories. I've looked at sub-repositories but that's not what I want since I need my repositories to work on

问题 I'm new to mercurial (and SCM in general) and I'm stuck at handling a parent child relationship between my two projects. One project is the parent project and is a subset of the other project (or rather, the other one is a superset of the first). I want to work on the two projects in a single local repository as if they were one but I want to publish them to two different public repositories. I've looked at sub-repositories but that's not what I want since I need my repositories to work on

问题 we are creating hospital information system software. The project will be different hospital to hospital and contain different use cases. But lots of parts will be the same. So we will use branching mechanism of the source control. If we find a bug in one hospital, how can we know the other branches have the same bug or not. IMAGE http://img85.imageshack.us/img85/5074/version.png The numbers in the picture which we attached show the each hospital software. Do you have a solution about this

问题 The following image is Git flow diagram, I'm very strange why Git need to design Index /Stage . You know the communication between Repository and Workspace is local, it's easy to commit or rollback between Repository and Workspace . Why does Git need to design Index /Stage ? Image 回答1: This is sort of a preview for changes about to be committed. You can, incrementally or in one go, constitute the future commit in this dedicated space, inspect what's in it, and commit only when you're

问题 If I have some code like /** * blah blah blah */ ...some codes... /** * yadda yadda And then I add /** * blah blah blah */ ...some codes... /** * blah blah blah */ ...some codes... before the "yadda yadda" commanet, the git diff will show that I added: + * blah blah blah + */ + ...some codes... + /** Is there a way to tell git, "hey, that's not right. Try again."? I know of --patience but that seems to just be for git diff and for the life of me it never works correctly. I know it's no super

问题 In SVN it is possible to use the 'repository browser' to browse an older revision of the trunk. That way you can see all folders and files belonging to this and previous revisions in the trunk. When folders and files have been moved this would be convenient to find them, not only a specific changeset. Is there a similar method to do this in the TFS source code explorer? It seems I can only see the latest revision in the browser. 回答1: Update If you want to browse a specific revision without

问题 I have a single SVN repository with two separate projects: project_1 /trunk /branches /1.0 /tags /1.0.0 project_2 /trunk /branches /1.0 /tags /1.0.0 As you can see, each has identical branch/tag numbers. Imagine there are different files in each project. I want to merge these into a single new project, project_3 . That is, the trunk of the new project will have all files/histories from the trunk of project_1 and project_2 , the 1.0 branch will have all files/histories from the 1.0 branches of

问题 For my Rails apps I normally deploy to production from a tagged version, and then display the tag in the user interface assigning the output of git describe --always to a variable in config/application.rb . Now I'm moving an app over to Heroku, and deployment to heroku only happens using the master branch, so this trick won't work any more. Are there any other ways to assign a version number to my code and display it on the UI when I've deployed to heroku? Thanks, Stewart 回答1: You can add a

问题 I'm beginning work on a project that will consist of a Ruby on Rails web application, an Android application, an iOS application, and a marketing website for these projects. I'm not quite sure how I want to structure this in source control. I'm using git (and GitHub) and I'm thinking I want all of the code in a single repository because I want to make use of the wiki and issues lists on GitHub without having a lot of separate projects to go to on GitHub. However, it seems to me like it would