blocks|key|3677655|text|时间向我们展示了最好的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3677656|我们的框架有了一个新的主要版本，完全转到了git。因此，基于旧版本的项目仍然通过SVN存储库进行维护，而新的开发是在git中运行的。|3677657|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Time has shown us the best solution. 

We switched to git completely with a new major version of our framework. So the projects based on an older version are still maintained through the SVN repository and the new development is running in git.

blocks|key|4522799|text|你做错了，™。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4522800|说真的，分支是为分支而设计的。您应该为不同的项目使用不同的存储库。|4522801|如果我没弄错的话，你有一个框架，还有几个基于这个框架的项目。无论您使用哪种版本控制系统，都会转换为框架的一个存储库，以及每个项目的一个存储库。|4522802|这就是git在你的工作副本中一次只显示一个分支的原因。您通常一次只能在一个分支上工作。如果您需要所有分支的工作副本，则每个分支需要一个工作副本。|4522803|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

You're doing it wrong™.

Seriously, branches are meant for, well, branches. You should use different repositories for different projects.

If I'm getting this right, you have a single framework you're working on, and several projects based on that framework. No matter what revision control system you use, that translates to one repository for the framework, and one repository for each project.

This is the reason git shows you only one branch at a time in your working copy. You usually work on a single branch at a time. You need one working copy per branch if you need to have working copies of all branches.

blocks|key|1095239|text|你可以用Git本身做类似的事情--参见Git+submodules。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1095240|这样，你就有了一个完整的"wwwroot“的Git代码库和每个项目的子模块。如果你只在几个项目中工作，你可以单独签出/克隆它们。|1095241|我从来没有发现git-svn是一个好的解决方案。我要么使用SVN，要么使用Git，而不是两者都使用。|1095242|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/docs/git-submodule^0|J|E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

You can do similar thing with Git itself - see <a href="http://git-scm.com/docs/git-submodule" rel="nofollow noreferrer">Git submodules</a>.

In this way you have a Git repo for whole "wwwroot" and submodules for each project. If your working only on a few projects of all you can check them out/clone separately.

I have never found git-svn to be a good solution. I either use SVN or Git, not both.

blocks|key|1095263|text|我自己刚从svn转到Git，我同意上面的两个答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1095264|我还建议不要使用git-svn+(除非将现有的svn存储库作为一次性的单向事件导入到Git中)。我还建议对每个项目使用单独的Git存储库。|1095265|使用svn，有些人喜欢使用单个存储库，因为它更容易在项目之间共享代码，等等。使用Git，您最好使用单个附加存储库来存储所有共享的内容；如果某个项目开始于某个项目，而您后来想要共享它，那么可以进行子树合并(顺便说一句，这是一个专门记录的Git术语)到您的共享存储库中。然后，您可以将代码拉回到其他项目中。|1095266|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Having just switched from svn to Git myself, I'd agree with the two answers above.

I'd also recommend against using git-svn (except perhaps to import your existing svn repositories into Git, as a once-off one-way event). And I'd also recommend using a separate Git repository for each project.

With svn, some people like to use a single repository because it's easier to share code between projects, etc. With Git, you're better using a single additional repository for all your shared stuff; if something starts out in one project and you later want to share it, do a subtree merge (that's a specifically-documented Git term, by the way) into your shared repository. Then you can pull the code back to your other projects.

blocks|key|4522966|text|正如其他人所说，使用单独的存储库，而不是分支。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4522967|有了SVN，你就可以..|4522968|http://svn/site_a/trunk/
http://svn/site_b/trunk/
etc|code-block|syntax|javascript|4522969|然后，您可以分别对每个站点执行svn+co+http://svn/site_a/trunk/|offset|length|style|CODE|4522970|使用git，您只需创建多个存储库：|4522971|mkdir+site_a
cd+site_a
git+init
cd+../
mkdir+site_b
cd+site_b
git+init|4522972|您可以有一个“主”存储库，每个站点都作为一个子模块添加，但这不是git-submodule的目的，我发现它的麻烦比它的价值更多。|4522973|除了将SVN+repo迁移到git，或者处理您无法控制的项目之外，使用git-svn做任何事情都不是一个好主意。|4522974|如果你想使用gits分支(还有其他好处)，为什么不完全切换到git呢？您可以使用类似gitosis的东西以某种类似SVN的集中式方式设置它。|4522975|基本上，如果你喜欢git，就切换到它(而不是使用git-svn)。如果您只是为了分支而使用git，请不要将SVN存储库拆分成较小的项目(site_a/trunk/等)。|4522976|entityMap|0|LINK|mutability|MUTABLE|url|http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way^0|0|0|0|F|V|0|0|0|W|D|0|Z|7|0|16|7|0|0|O|7|1W|D|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1B|8|@$K|1C|L|1D|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1F|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|1G|8|@$K|1H|L|1I|M|N]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1J|8|@$K|1K|L|1L|M|N]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1M|8|@]|9|@$K|1N|L|1O|1|1P]]|A|$]]|$1|Y|3|Z|5|6|7|1Q|8|@$K|1R|L|1S|M|N]|$K|1T|L|1U|M|N]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

As others have said, use separate repositories, not branches.

With SVN, you could just have..

<pre><code>http://svn/site_a/trunk/
http://svn/site_b/trunk/
etc
</code></pre>

Then you can <code>svn co http://svn/site_a/trunk/</code> each site separately

With git, you would just create multiple repositories:

<pre><code>mkdir site_a
cd site_a
git init
cd ../
mkdir site_b
cd site_b
git init
</code></pre>

You could have a "master" repository with each site added as a sub-module, but this is not what <code>git-submodule</code> is intended for, and I found it more trouble than it's worth.

It's not a very good idea to use <code>git-svn</code> for anything more than migrating an SVN repo to git, or working on a project you don't control.

If you want to use gits branching (and it's other benefits), why not switch entirely to git? You can set it up in a somewhat-SVN-like centralised-fashion, using something like <a href="http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way" rel="nofollow noreferrer">gitosis</a>

Basically, if you like git, switch to it (rather than using <code>git-svn</code>). If you are looking at git just for the branching, do not - split your SVN repository into smaller projects (<code>site_a/trunk/</code> and so on)

we use SVN for our work. We are a small web design studio and we write in PHP developing some kind of "framework" in the mean time.

Now we are thinking about a more powerful solution and we would like to try git-svn. We use branches as different projects — one branch, one project. So I have in my computer exactly the same structure as in my wwwroot. One branch = one project = one virtualhost.

As I played with git-svn I don't know how to achieve this with it. I need the branches to be physically present in the filesystem because I have virtulhosts in Apache etc.

Can you please give me some advice or point me to some tutorial how to do it?

Git-SVN for Web development — how to do it?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们在工作中使用SVN。我们是一个小型的网页设计工作室，同时我们用PHP编写开发某种“框架”。现在我们正在考虑一个更强大的解决方案，我们想尝试一下git-svn。我们使用分支作为不同的项目-一个分支，一个项目。所以我的电脑和我的wwwroot的结构是一样的。一个分支=一个项目=一个虚拟主机。当我使用git-svn时，我不知道如何使用它来实现这一点。我需要分支以物理方式存在于文件系统中，因为我在Ap

问用于Web开发的Git-SVN -如何实现？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于Web开发的Git-SVN -如何实现？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于Web开发的Git-SVN -如何实现？
EN