version-control

问题 I got a laptop in preparation for the coming semester, which will see me taking a university programming course while working full time. I will, of course, be using a source control system (probably Subversion) and had the idea of creating my repositories in my Dropbox folder, which would enable me to check out and work on code locally using my laptop or my desktop (or, indeed, any other computer that can access the Internet), and then commit it back to the shared Dropbox repository. Any

问题 I have a small amount of experience using SVN on my development projects, and I have just as little experience with relational databases. I know the basic concepts like tables, and SQL statements, but I'm far from being an expert. What I'd like to know is if there are any generic version control type systems like SVN, but that work with a database rather than files. I would like the same kind of features you get with SVN like the ability to create branches, create tags, and merge branches

问题 I have a small amount of experience using SVN on my development projects, and I have just as little experience with relational databases. I know the basic concepts like tables, and SQL statements, but I'm far from being an expert. What I'd like to know is if there are any generic version control type systems like SVN, but that work with a database rather than files. I would like the same kind of features you get with SVN like the ability to create branches, create tags, and merge branches

问题 I am looking at putting a code base that runs several website into version control. There are several instance of this code base running websites on different virtual servers. The problem I'm grappling with is that each of these separate instances of more or less the same code have sub-directories with site-specific functions. But it seems that version control systems want to control the entire directory hierarchy. For instance, each instance has the directory /www/smarty/libs/plugins/ Where

问题 I'm using Rubberduck (Version 2.0.13) in combination with a local git repository for version control of my VBA project. Currently, I need to re-open the repository every time I start Rubberduck using Manage -> Open Existing Repository in the Source Control Window. Is there a better way to handle the local repository, e.g. can Rubberduck save this setting? I don't want to use an online repository, so I think the "Unsynced commits" tab is irrelevant for me. 回答1: This started as a comment, but

问题 I'm using Rubberduck (Version 2.0.13) in combination with a local git repository for version control of my VBA project. Currently, I need to re-open the repository every time I start Rubberduck using Manage -> Open Existing Repository in the Source Control Window. Is there a better way to handle the local repository, e.g. can Rubberduck save this setting? I don't want to use an online repository, so I think the "Unsynced commits" tab is irrelevant for me. 回答1: This started as a comment, but

问题 If I create a test suite for a development project, should those classes be kept under version control with the rest of the project code? 回答1: Yes, there is no reason not to put them in source control. What if the tests change? What if the interfaces change, necessitating that the tests change? 回答2: Yes, all the same reasons you put production code in to source control still apply to any unit tests you write. It's the classic who, where and why questions: Who changed the code? When did they

问题 Whenever I try to use a pre commit hook to prepend the current branch name, a sh.exe.stackdump file is generated and the hook doesn't work. I've tried a number of other files which have been verified to work on other PC's leading me to believe it's not an issue with the hook itself. I'm using git 2.18 on Windows 10. I've verified my PATH is correct, reinstalled git already and have no AV running other than Windows Defender. Stackdump: Exception: STATUS_STACK_OVERFLOW at rip=7FFE4951EC07 rax

问题 I've recently started working on a new project for which the development team is using ClearCase for version control (the project is coded mostly in java and ExtJs). I'm hearing the terms 'View' and 'Branch' being thrown around a lot - are these terms interchangeable? If not, could you please provide a layman's explanation of a View and a Branch and how they relate to each other. Are Views and Branches particular to ClearCase or are these terms used in other version control systems as well?

问题 I have the following folder structure for my project src/ test_unit/ package1/ test_unit/ package2/ test_unit output/ In my devel branch all folders should be version controlled, but the master/stable branch should ignore and not merge test_unit/ and output/ folder. How can I achieve this? With .gitignore it won't work because .gitignore will be merged between the branches. 回答1: Try a combination of .gitignore and .gitattributes files: in master/stable branch, you could have .gitattributes