SVN 是否在任何地方显示分支层次结构?

发布于 2024-10-07 02:22:23 字数 235 浏览 5 评论 0原文

我的 SVN 存储库中有一个名为“Version4”的分支
现在我在这个分支中创建了另一个名为“Version4.5”的分支,因此该分支的父分支应该是“Version4”分支。
这个层次结构是否显示在 SVN 视图中的某个位置?因为当我打开存储库浏览器时,我可以看到这两个分支的文件夹并排位于同一级别,而不是一个在另一个下。
也许层次结构对 SVN 来说根本不重要,我可以从任何分支合并到任何分支(即使从逻辑上讲它没有意义)?

I Have got in my SVN's repositry a branch called 'Version4'
now I created out of this branch another branch called 'Version4.5' so that the parent of this branch should be 'Version4' branch.
Is this hierarchy shown somwhere in SVN views? because when I open the repository browser I can see the folders of these 2 branches side by side in the same level and not one beneath the other.
Perhaps the hierarchy doesn't matter at all to SVN and I can merge from any branch to any branch (even if logically it doesn't make sense)?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

零時差 2024-10-14 02:22:23

也许层次结构对 SVN 来说根本不重要,我可以从任何分支合并到任何分支(即使从逻辑上讲它没有意义)?

Subversion 存储库中目录树的布局确实一点也不重要。拥有名为“trunk”、“tags”、“branches”的文件夹并像这样使用它们只是一种约定(但当然是一个非常有用的约定)。

您可以通过检查版本历史记录来查看哪个分支是从哪个其他分支(或标记或其他)创建的。它将显示为创建分支的 COPY 命令的源路径。

我强烈建议您使用 GUI 工具或类似 Trac 的工具,以便能够轻松地调查这些事情。

Perhaps the hierarchy doesn't matter at all to SVN and I can merge from any branch to any branch (even if logically it doesn't make sense)?

The layout of the directory tree in a subversion repository does indeed not matter at all. Having folders called "trunk", "tags", "branches" and using them as such is a mere convention (but of course a very useful one).

You can see what branch was created off which other branch (or tag, or whatever) by inspecting the version history. It will show up as the source path of the COPY command that created the branch.

I strongly recommend you use a GUI tool or something like Trac to be able to comfortably investigate these things.

眼中杀气 2024-10-14 02:22:23

在 Subversion 中,分支和标记是通过常规目录复制来完成的;这不是一个bultin概念,也没有什么特别的。您在进行复制时选择的存储库浏览器中显示的位置。如果您对此不满意,可以照常移动东西。分支之间存在的唯一物理关系是:

  • 共同祖先(分支之前)
  • 合并历史(分支之后)

In Subversion, branching and tagging are accomplished through regular directory copy; it's not a bultin concept and it hasn't anything special. The location displayed in the repository browser in the one you chose when doing the copy. If you are not happy with it, you can move stuff around as usual. The only physical relationships that exists between branches are:

  • Common ancestors (before branching)
  • Merge history (after branching)
我做我的改变 2024-10-14 02:22:23

哪个存储库浏览器 - Web 界面?这是整个存储库的最新(或固定)修订版的非常简单的视图。

如果您使用 1.5+ 服务器和客户端,那么您可能拥有的最好的方法是每个版本的根目录下有一个 svn:mergeinfo 属性,

svn propget svn:mergeinfo http://myserver/svn/branches/version4.5/

其中列出了任何复制和复制的源分支和版本。合并你已经完成了。我认为第一个条目将是创建该分支的原始条目。

Which repository browser - the web interface? That's a very simple view on the latest (or a pegged) revision for the whole repository.

If you're using 1.5+ server and client then the best you're likely to have is an svn:mergeinfo property at the root of each revision,

svn propget svn:mergeinfo http://myserver/svn/branches/version4.5/

which lists the source branches and revisions of any copying and merging you've done. I think the first entry will be the original this branch was created from.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文