[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: English terminology / explanation needed

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-05-25 14:53:28 CEST

These error messages are pretty specific to certain subcommands, so let
me give you some context:

On Tue, 2004-05-25 at 02:30, Lübbe Onken wrote:

> Here we go:
> libsvn_client/ra.c:443
> "Missing changed-path information for '%s' in revision %ld"
> what is a changed-path information and why is it missing?

This happens when the 'log' command expects to see a certain path
mentioned in the list of "changed paths", but it isn't there. If you
run 'svn log -v', you'll see that -v switch shows the list of changed
paths for each revision.

> libsvn_client/ra.c:704
> "'%s' in revision %ld is an unrelated object"
> unrelated to what?

The user has run a subcommand of the form

   'svn subcommand foo.c -r X'

Where X is a revision in the "future", i.e. some revision larger than
the working revision of foo.c.

This error happens when the svn client discovers that foo.c@X is a
completely different object from the foo.c in the working copy
(foo@BASE); they're "unrelated objects". This happens, for example, if
sombody deletes foo.c in revision X-1, and then re-adds a new file with
the same name in revision X.

> clients/commandline/notify.c:300
> "Status against revision: %6ld\n"
> Does this mean "Status in revision" ? "Against" translates funny and
> doesn't make sense.

This is English shorthand for:

"The status command was performed against revision X."

You only see this when you run 'svn status -u'. The -u switch contacts
the repository and compares the working copy to HEAD, in order to show
which files are out-of-date. This message tells people the exact
revision of HEAD: "I compared your working copy to HEAD, which is
currently revision X."

> include/svn_error_codes.h:683
> "Svndiff data contains backward-sliding source view"
> What the Dickens is a "backward-sliding source view" ?

There's no way to explain svndiff encoding here. :-)
In a nutshell, svndiff is our way of encoding binary diffs. It operates
on "windows" that "slide" across the data as the diff is performed. The
binary diff algorithm refers to the original data by discussing offsets
into the current window. I think this error is complaining that an
svndiff operation is attempting to talk about data that the window has
already moved past.

> include/svn_error_codes.h:829
> "Python exception has been set with the error"
> what has really happened? Has a python exeption occured? Where's the
> rest of the sentence? What kind of error?

When the python-swig bindings throw a python exception, this needs to be
converted into an svn_error_t in C. I think this is is just a generic
error description that means: "the python bindings threw a python

But I agree: the grammar makes no sense to me here. Maybe cmpilato or
someone with swig-py experience can explain the grammar. I don't
understand what "set with the error" means.

> libsvn_ra_dav/fetch.c:2314
> "REPORT response handling failed to complete the editor drive"
> Err what?

REPORT is an http method, part of webdav. Editors are the mechanisms by
which trees are changed. An "editor" is a table of functions which,
when called by a "driver" process, causes a tree to change. Yes, this
error message assumes you are a developer, not a user. :-)

Don't translate the word "REPORT": that's a webdav method. I guess you
can translate "editor" and "driver" (==> "editor" is the same word auf
Deutsch, nein? And the noun "drive" is tricky, some noun form of
"steuern", maybe?)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 25 14:58:43 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.