confusing example in the SVN book

In the current SVN book (nightly):

  It's easy to use SSH in conjunction with svnserve. The client simply
  uses the svn+ssh:// URL scheme to connect:

  $ whoami
  harry

  $ svn list svn+ssh://host.example.com/repos/project
  harry_at_host.example.com's password: *****

  foo
  bar
  baz
  …

  In this example, the Subversion client is invoking a local ssh
  process, connecting to host.example.com, authenticating as the user
  harry, then spawning a private svnserve process on the remote
  machine running as the user harry. The svnserve command is being
  invoked in tunnel mode (-t), and its network protocol is being
  “tunneled” over the encrypted connection by ssh, the tunnel agent.
  svnserve is aware that it's running as the user harry, and if the
  client performs a commit, the authenticated username will be used
  as the author of the new revision.

But the book doesn't say which "harry" (the client's or the server's)
is taken into account as the author of the new revision; "authenticated
username" suggests that it's the server's and this is also said a bit
later in the book (though not all users may read that part), but this
doesn't appear clearly in the example (and the word "aware" above may
be confusing since it could mean that the client gave some information,
which is not the case). You should probably give an example with two
different user names on the client and on the server. This could be:

  $ whoami
  harryc

  $ svn list svn+ssh://host.example.com/repos/project
  harrys_at_host.example.com's password: *****

  foo
  bar
  baz
  …

  In this example, the Subversion client is invoking a local ssh
  process, connecting to host.example.com, authenticating as the user
  harrys (according to SSH user configuration), then spawning a private
  svnserve process on the remote machine running as the user harrys.
  The svnserve command is being invoked in tunnel mode (-t), and its
  network protocol is being “tunneled” over the encrypted connection
  by ssh, the tunnel agent. If the client performs a commit, the
  authenticated username harrys will be used as the author of the new
  revision.

This makes clear that the user name on the *server* side is taken
into account as the author of the new revision.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org