CollabNet Subversion Edge 忽略文件

发布于 2024-11-10 01:45:05 字数 224 浏览 2 评论 0原文

我在子版本控制方面是全新的,所以请耐心等待。

我使用 CollabNet 的 Subversion Edge 来管理我在 Eclipse IDE 中构建的基于 PHP/ActionScript 的项目的存储库。在我的项目的根文件夹中,Eclipse 包含几个与该项目不直接相关的配置文件。如何通过 CollabNet 设置我的存储库以忽略这些文件/文件夹?是通过“存储库访问规则”吗?

感谢您抽出时间。

I am brand new at sub-versioning, so please bear with me.

I use CollabNet's Subversion Edge to manage a repository for a PHP/ActionScript based project I am building in the Eclipse IDE. In my project's root folder, Eclipse included several configuration files that aren't directly related to the project. How can I set up my repository to ignore these files/folders via CollabNet? Would it be through the "Repository Access Rules"?

Thank you for your time.

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

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

发布评论

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

评论(1

-柠檬树下少年和吉他 2024-11-17 01:45:05

第 3 章高级主题“忽略未版本控制的项目” '”似乎适合您的设置:

摘录:

[...] 但是这些未进行版本控制的文件和目录可能会给 Subversion 用户带来一些烦恼。
例如,因为 svn addsvn import 命令默认情况下以递归方式运行,并且不知道您希望和不希望对给定树中的哪些文件进行版本控制,很容易意外地将无意的内容添加到版本控制中。
而且,由于 svn status 默认情况下会报告工作副本中感兴趣的每个项目(包括未版本控制的文件和目录),因此在存在许多此类项目的情况下,其输出可能会变得相当嘈杂。

因此 Subversion 提供了两种方法来告诉它您希望它忽略哪些文件。

  • 其中一种方法涉及使用 Subversion 的运行时配置系统(请参阅“运行时配置区域”一节),因此适用于使用该运行时配置的所有 Subversion 操作,通常是在特定计算机上执行的操作,或由计算机的特定用户。
  • 另一种方式利用 Subversion 的目录属性支持,与版本树本身的绑定更紧密,因此会影响拥有该树工作副本的每个人。这两种机制都使用文件模式。

Subversion 运行时配置系统提供了一个选项,global-ignores,其值是以空格分隔的文件模式集合(也称为 glob)。
Subversion 客户端根据要添加到版本控制的候选文件的名称以及 svn status 命令注意到的未版本化文件的名称来检查这些模式。
如果任何文件的名称与其中一种模式匹配,Subversion 基本上会认为该文件根本不存在。
这对于您几乎不想对其进行版本控制的文件类型非常有用,例如 Emacs 的 *~.*~ 文件等编辑器备份文件

The "Chapter 3. Advanced Topics 'Ignoring Unversioned Items'" seems appropriate for your setup:

Extract:

[...] But these not-to-be-versioned files and directories can cause some annoyance for Subversion users.
For example, because the svn add and svn import commands act recursively by default, and don't know which files in a given tree you do and don't wish to version, it's easy to accidentally add stuff to version control that you didn't mean to.
And because svn status reports, by default, every item of interest in a working copy–including unversioned files and directories–its output can get quite noisy where many of these things exist.

So Subversion provides two ways for telling it which files you would prefer that it simply disregard.

  • One of the ways involves the use of Subversion's runtime configuration system (see the section called “Runtime Configuration Area”), and therefore applies to all the Subversion operations which make use of that runtime configuration, generally those performed on a particular computer, or by a particular user of a computer.
  • The other way makes use of Subversion's directory property support, is more tightly bound to the versioned tree itself, and therefore affects everyone who has a working copy of that tree. Both of the mechanisms use file patterns.

The Subversion runtime configuration system provides an option, global-ignores, whose value is a whitespace-delimited collection of file patterns (also known as globs).
The Subversion client checks these patterns against the names of the files which are candidates for addition to version control, as well as to unversioned files which the svn status command notices.
If any file's name matches one of the patterns, Subversion will basically act as if the file didn't exist at all.
This is really useful for the kinds of files that you almost never want to version, such as editor backup files like Emacs' *~ and .*~ files

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