通过索引获取字符串字符 - Java(Get string character by index - Java)

 哪个最适合你，取决于你的需要，欲望和工作流程。 他们在某种意义上是半同构的，只是一些比别人更容易使用，用于特定的任务。 
 
 
 
 当您在与子项目不同的时间内在子项目上进行控制和开发时， gitslave非常有用，此外，当您通常要同时标记，分支，推，拉等所有存储库时。 gitslave从来没有在我知道的Windows上测试过。 它需要perl。 
 
 
 当您不控制子项目或更具体地希望将子项目修改为特定版本时，即使子项目发生变化， git-submodule也会更好。 git-submodule是git的标准部分，因此可以在windows上工作。 
 
 
 git-subtree为git的内置子树合并策略提供了前端。 当您更喜欢拥有单一存储库“统一”git历史记录时，情况会更好。 与子树合并策略不同的是，将更改导出到不同的（目录）树更简单的原始项目，但它不像gitslave甚至git-submodule那样自动。 
 
 
 在理论上， 回购与gitslave相似，但并没有记录我发现的非android操作。 它相当致力于Google Android开发模式，并且只能原生支持少量的git命令（尽管可以运行任意命令），并且有限的本地支持不支持，例如，集中的存储库来推送和检出分支似乎相当困难。 
 
 
 如果您使用多个版本控制系统，kitenet的mr将是您想要使用的，但是由于其最低的公分母方法，因此主要限于git-only超级项目。 有些方法可以运行任意命令，但是它们的集成度并不理想。 
 

Which is best for you depends on your needs, desires, and workflow. They are in some senses semi-isomorphic, it is just some are a lot easier to use than others for specific tasks.
 
 
 
gitslave is useful when you control and develop on the subprojects at more of less the same time as the superproject, and furthermore when you typically want to tag, branch, push, pull, etc all repositories at the same time. gitslave has never been tested on windows that I know of. It requires perl.
 
 
git-submodule is better when you do not control the subprojects or more specifically wish to fix the subproject at a specific revision even as the subproject changes. git-submodule is a standard part of git and thus would work on windows.
 
 
git-subtree provides a front-end to git's built-in subtree merge strategy. It is better when you prefer to have a single-repository "unified" git history. Unlike the subtree merge strategy, it is easier to export changes to the different (directory) trees back out to the original project, but it is not as automatic as it is with gitslave or even git-submodule.
 
 
repo is in theory similar to gitslave, but not as well documented for non-android operations that I have found. It is fairly dedicated to the Google Android development model and only natively supports a handful of git commands (though you can run arbitrary commands) and the limited native support doesn't support, for example, a centralized repository to push to and checking out a branch seems fairly difficult.
 
 
kitenet's mr is what you would want to use if you have multiple version control systems in use, but is mostly limited for git-only superprojects due to its lowest common denominator approach. There are ways to run arbitrary commands, but they are not as well integrated.