version-control

问题 I have a flat svn repository which looks like: my_repo/ ├── file1.c ├── file2.c ├── file3.c └── README This repo has no branches, or tags and all I am trying to do is convert it to a git repository and maintain the commit history. I have tried: git svn clone --trunk=/ -A users.txt svn+ssh://user@svn.example.com/projects/my_repo dest_dir Which I assumed would work, however, when I navigate into dest_dir and perform git svn fetch , it doesn't seem to fetch anything. Using git log yields: fatal:

问题 I have list of submodules in .gitmodules. I want to download a specific submodule i.e grpc only if there is some option enabled as true in config file. Since grpc is not required at times for my build. All submodules are in third-party directory. So .gitmodules is like: [submodule "third-party/libzip"] path = third-party/libzip url = https://github.com/nih-at/libzip.git [submodule "third-party/sqlite"] path = third-party/sqlite url = https://github.com/mackyle/sqlite.git branch = sqlite-3.23

问题 I'm trying to implement database source control. the tool I need should create a separate file for each object in the database, preferably arranged in folders, like stored procedures functions views tables and it would be great being able to also dump the results of certain queries, in order to keep track of the data changes in several configuration tables... I wonder if there's is already a tool that can handle this kind of stuff... -- just to clear a few things... I'm already using sql

问题 Does it make any sense to somehow store an "uncompressed" version of normally-compressed files in the repository? If so, is there a standard way to implement this? (Perhaps a standard pre-commit hook that uncompresses each such file into a specially-named folder; and a post-checkout hook that compresses such specially-named folders into the compressed files that LibreOffice knows how to read and write? Something like the process described by "Should I decompress zips before I archive?" ?)

问题 When I check in code to our Team Foundation Server, I some times (probably more often than I actually do...) should associate my check-in with a task or a bug I am working towards. When I mark a task or a check in, it sets the Check-in Action to Resolve. But almost always, I just want to have it as just Associate. The result is that I often end up marking a task as resolved by mistake. Is there a way to make Associate the default when I mark a task? Resolving a bug or a task should be

问题 I think I misunderstand something but can’t find what exactly. I googled, but didn't get the idea. There are two popular techniques – continuous integration and distributed source code control. People somehow combine them, but I don’t understand how. AFAIK, continuous integration means commit to the central repository (push) as soon as you’ve tested your code locally. At the same time, distributed systems are loved so much, among other things, because you can commit and commit and commit

问题 I am trying to learn how to use git cherry pick, I read the manual pages that git returns by doing git cherry-pick --help but that did not seem to help. I will try and explain the problem below. I have two branches master and other . On branch master The commit history is 0x2 Second commit from master branch 0x1 Initial commit And the only file in the repository that I am tracking readme has the following contents Some text On branch other The commit history is 0x5 CHECKPOINT, going to cherry

问题 Is to possible to "purge" history from a given change set/date in TFS? So, for example, For file X destroy all version older than date Y. or destroy all version before revision Y. 回答1: Yes you can - http://msdn.microsoft.com/en-us/library/bb386005.aspx - TF Destroy $/MyTeamProject /keephistory /stopat:C864 来源： https://stackoverflow.com/questions/3965361/is-it-possible-to-do-a-destroy-history-in-tfs

问题 Normally, Mercurial will abort if I have a dirty working copy when I try to import a patch: $ hg import x.patch abort: outstanding uncommitted changes Is it possible to import it anyway? 回答1: With Mercurial 1.9, you can use hg import --bypass to apply a patch without touching the working copy. The patch will be applied on the working copy parent revision by default. Use the --exact flag to apply the patch onto the changeset mentioned in the patch header instead. 回答2: If you are using

问题 I was looking for a way to put my existing project under source control, and I looked at this question, but it looks like that solution only worked with Xcode 4.0 because I can't find a way to do what is advised. I also looked at this question, but that solution doesn't work either because my project isn't currently under source control. How can I get my existing project under source control? Edit I want it to be a git repository, not subversion. 回答1: you can do it in terminal using: cd /to