version-control

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 3 months ago . I was reading a blog where the writer said this "Code doesn’t exist unless it’s checked into a version control system. Use version control for everything you do. Any version control, SVN, Git, even CVS, master it and use it." I have never used any sort of version control and

问题 First, I know about this: How would you organize a Subversion repository for in house software projects? Next, the actual question: My team is restructuring our repository and I'm looking for hints on how to organize it. (SVN in this case). Here's what we came up with. We have one repository, multiple projects and multiple svn:externals cross-references \commonTools /*tools used in all projects. Referenced in each project with svn:externals*/ \NUnit.v2.4.8 \NCover.v.1.5.8 \<other similar

问题 First, I know about this: How would you organize a Subversion repository for in house software projects? Next, the actual question: My team is restructuring our repository and I'm looking for hints on how to organize it. (SVN in this case). Here's what we came up with. We have one repository, multiple projects and multiple svn:externals cross-references \commonTools /*tools used in all projects. Referenced in each project with svn:externals*/ \NUnit.v2.4.8 \NCover.v.1.5.8 \<other similar

问题 The way you Git ignore watching/tracking a particular dir/file. you just run this: git update-index --assume-unchanged <file> Now how do you undo it so they are watched again? (Let's call it un-assume.) 回答1: To get undo/show dir's/files that are set to assume-unchanged run this : git update-index --no-assume-unchanged <file> To get a list of dir's/files that are assume-unchanged run this : git ls-files -v|grep '^h' 回答2: If this is a command that you use often - you may want to consider having

问题 Our team has just moved from Netbeans to Intellij 9 Ultimate and need to know what files/folders should typically be excluded from source control as they are not "workstation portable", i.e.: they reference paths that only exist on one user's computer. As far as I can tell, Intellij wants to ignore most of the .idea project including .idea/artifacts/* .idea/inspectionProfiles/* .idea/copyright/* .idea/dataSources.ids .idea/dataSources.xml .idea/workspace.xml However, it seems to want to check

问题 Our team has just moved from Netbeans to Intellij 9 Ultimate and need to know what files/folders should typically be excluded from source control as they are not "workstation portable", i.e.: they reference paths that only exist on one user's computer. As far as I can tell, Intellij wants to ignore most of the .idea project including .idea/artifacts/* .idea/inspectionProfiles/* .idea/copyright/* .idea/dataSources.ids .idea/dataSources.xml .idea/workspace.xml However, it seems to want to check

问题 Which is the correct name for a system which stores versions of source code, like SVN or TFS? I've always called it source control, but places like Wikipedia calls it revision control? To make this more complicated sites like this one have a tag for both? 回答1: Revision Control is the more generic term, used for source-control tools but also for other tools (Word, OpenOffice, ...). It references a version. Source Control offers revision control with branching and merging which are not always

问题 Is it possible to have gitlab setup to automatically sync (mirror) a repository hosted at another location? At the moment, the easiest way I know of doing this involves manually pushing to the two (gitlab and the other) repository, but this is time consuming and error prone. The greatest problem is that a mirror can resynchronize is two users concurrently push changes to the two different repositories. The best method I can come up with to prevent this issue is to ensure users can only push

问题 I'm looking for ways to reduce the size of a git repository. Searching leads me to git gc --aggressive most of the times. I have also read that this isn't the preferred approach. Why? what should I be aware of if I'm running gc --aggressive ? git repack -a -d --depth=250 --window=250 is recommended over gc --aggressive . Why? How does repack reduce the size of a repository? Also, I'm not quite clear about the flags --depth and --window . What should I choose between gc and repack ? When

问题 This actually stems from on my earlier question where one of the answers made me wonder how people are using the scm/repository in different ways for development. 回答1: Pre-tested commits Before (TeamCity, build manager): The concept is simple, the build system stands as a roadblock between your commit entering trunk and only after the build system determines that your commit doesn't break things does it allow the commit to be introduced into version control, where other developers will sync