Question

当我从unix命令行执行svn commit时，它会在打开编辑器之前切换到父目录。当我做贝壳逃生时，这引起了极大的困惑，因为我不在我认为的地方。

这种行为的原因是什么？

（编辑）下面的屏幕截图显示在最低目录中发生这种情况，而不是在最顶层目录中发生

svn --version svn, version 1.5.5 (r34862)

test: svn checkout file:///export/home/svn/xxx/a
A    a/b
A    a/b/c
A    a/b/c/new
Checked out revision 8882.

test: cd a/b/c
test: pwd
/home/geretz/test/a/b/c
test: echo changed > new
test: svn commit

--This line, and those below, will be ignored--

M    c/new
~
~
:!pwd
/home/geretz/test/a/b

Hit ENTER or type command to continue

中止编辑会话，尝试从顶级目录提交

test: pwd
/home/geretz/test/a/b/c
test: cd ../..
test: pwd
/home/geretz/test/a
test: svn commit

--This line, and those below, will be ignored--

M    b/c/new
~
~
:!pwd
/home/geretz/test/a

Hit ENTER or type command to continue

Answer 1

如果您浏览svn来源，则会发现svn commit由http://svn.apache.org/repos/asf/subversion/branches/1.5.x/subversion/svn/commit-cmd.c中的svn_cl__commit功能处理。负责将pathes拆分为'basename'和'dirname'的实际函数是svn_wc_get_actual_target。此函数在http://svn.apache.org/repos/asf/subversion/branches/1.5.x/subversion/include/svn_wc.h中声明，并具有以下注释：

/** Conditionally split @a path into an @a anchor and @a target for the
 * purpose of updating and committing.
 *
 * @a anchor is the directory at which the update or commit editor
 * should be rooted.
 *
 * @a target is the actual subject (relative to the @a anchor) of the
 * update/commit, or "" if the @a anchor itself is the subject.
 *
 * Allocate @a anchor and @a target in @a pool.
 */

最后在文件http://svn.apache.org/repos/asf/subversion/branches/1.5.x/subversion/libsvn_wc/update_editor.c中，我们可以看到以下评论：

Updates are accomplished by driving an editor, and an editor is
"rooted" on a directory.  So, in order to update a file, we need to
break off the basename of the file, rooting the editor in that
file's parent directory, and then updating only that file, not the
other stuff in its parent directory.

Secondly, we look at the case where we wish to update a directory.
This is typically trivial.  However, one problematic case, exists
when we wish to update a directory that has been removed from the
repository and replaced with a file of the same name.  If we root
our edit at the initial directory, there is no editor mechanism for
deleting that directory and replacing it with a file (this would be
like having an editor now anchored on a file, which is disallowed).

All that remains is to have a function with the knowledge required
to properly decide where to root our editor, and what to act upon
with that now-rooted editor.  Given a path to be updated, this
function should conditionally split that path into an "anchor" and
a "target", where the "anchor" is the directory at which the update
editor is rooted (meaning, editor->open_root() is called with
this directory in mind), and the "target" is the actual intended
subject of the update.

svn_wc_get_actual_target() is that function.

...

As it turns out, commits need to have a similar check in place,
too, specifically for the case where a single directory is being
committed (we have to anchor at that directory's parent in case the
directory itself needs to be modified)

为什么subversion在执行提交时会切换到父目录

1 个答案: