使用不带/ trunk结构的TortoiseSVN创建分支 [英] Creating a branch with TortoiseSVN without /trunk structure

查看:320
本文介绍了使用不带/ trunk结构的TortoiseSVN创建分支的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

背景:我们将源代码保存在我们自己服务器上的SVN存储库中。我们有A小组负责网站的主要功能。我们希望与B团队一起在不同的位置进行设计。

Background: We have our source code saved in an SVN repository at our own server. We have Team A working on the main functionality of the website. We are looking to work with a Team B on the design aspects which will be at a different location.

很久以前,在建立SVN信息库时,我创建了它的结构最终可以在以下位置访问:

A long time back when setting up the SVN repository, I created it with a structure which was finally accessible at:

svn://www.myserver.com/main/abc

源代码文件位于 abc级别及其下的文件夹中。

The source code files are present at the 'abc' level and in folders below that.

这对我们来说一直很好,直到现在我需要创建一个分支。选择TortoiseSVN→分支/标记似乎可以让我选择在以下位置创建分支:

This has been working fine for us until now when I need to create a branch. Choosing TortoiseSVN → Branch/Tag seems to give me the option of creating a branch at:

svn://www.myserver.com/main/def

但是,当我最后一次尝试时,它似乎创建了一个WITHIN文件夹abc命名为 def,这根本不是我所期望的。我希望为团队B创建一个完全独立的存储库副本,并且当需要将两者合并时-可能会尽可能顺利地进行。

However, when I tried it last, it seemed to create a folder WITHIN 'abc' named 'def' which wasn't what I was expecting at all. I was hoping to create a completely separate copy of the repository which Team B could work on, and when it came time to merge the two - that could happen as smoothly as possible.

[我知道在提交'abc'中的更改时,我们还必须提交'def']

[I understand that when committing changes in 'abc', we will also have to commit in 'def']

推荐答案

Hvd答案的扩展版本



存储库布局无非是关于使用树的公认协议。您可以将主线和边线存储在存储库树的任何位置,而它们不会相交。

Extended version of Hvd's answer

Repository layout is nothing more than accepted agreement about using tree. You can store mainline and side-work in any place of repository tree, while they aren't intersected.

在您对回购当前状态的描述中,您会错过重要的一件事存储库根在哪一级? 这两种情况 / main /和 abc / 都是可以解决的,但是步骤不同。

In your description of current state of repo you miss one important thing: Where is repository root, on which level? Both situations "/main/" and "abc/" are solvable, but with different steps.

您可以使用TSVN的存储库浏览器轻松检测甚至是根目录。您可以通过存储库访问svn://www.myserver.com/main/ URL还是会出错?

You can easy detect root even remote, using TSVN's Repository Browser. Can you access svn://www.myserver.com/main/ URL as repository or you'll get error?

与回购根相关的第二个问题是 TeamA现在使用哪个URL访问仓库?是的,我已阅读并理解

Second question, related to repo-root is "Which URL TeamA use now for accessing repo?" Yes, I read and understand


结构,该结构最终可在svn://www.myserver.com/main/abc

structure which was finally accessible at svn://www.myserver.com/main/abc

,但它为假设保留了一些空间:

but it leave some space for assumptions:


  • 从svn://www.myserver.com/main/进行TeamA签出,并在工作副本中包含ABC目录

  • 从svn://www.myserver.com/main/进行TeamA签出abc,并立即在根目录中有wotking空间

(第一个版本和svn://www.myserver.com/main作为根目录,来自Q1将需要稍后重新检出存储库,以排除TeamB空间的公共根)

(first version and svn://www.myserver.com/main as root from Q1 will require later re-checkout repository in order to exclude common root with TeamB space)

查找回购根目录,为我们写下来,无论如何我们都会概述下一步

Find Repo-root, write it for us, we'll outline next steps in any case

这篇关于使用不带/ trunk结构的TortoiseSVN创建分支的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆