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

Re: svn commit: rev 2684 - trunk/subversion/include trunk/subversion/mod_dav_svn trunk/subversion/clients/cmdline trunk/subversion/libsvn_repos trunk/subversion/libsvn_ra_dav

From: <cmpilato_at_collab.net>
Date: 2002-07-25 15:59:53 CEST

Nuutti Kotivuori <naked@iki.fi> writes:

> cmpilato@collab.net wrote:
> >> But I don't get this? Why do we hide 'M' as an action, and instead
> >> show 'U'?
> >
> > The 'M' is simply more "correct" for internal purposes. The 'U'
> > that the client binary prints exists only for consistency with the
> > kind of output 'svn update' yields.
> Oh, so there is no 'U' coming out as an action anymore, they are all
> 'M'? Or is there both 'U' and 'M' coming out and we just don't want to
> tell the user the distinction?

Sorry. I've managed to confuse you.

From the server, there can be only 4 action tokens:

   M)odify (this used to be 'U', but was changed to 'M' because other
             items in the API referred to "modify" instead of "update")

The client, however, wants its output to be consistent with that of
`svn update', so it maps like so:

   A => A
   D => D
   R => R
   M => U

Basically, we had:

   svn_fs_path_change_modify => U => (network) => M

and now we have:

   svn_fs_path_change_modify => M => (network) => U

where this part here ^^^^^^^^^^^^ feels more "right" to me now.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 25 16:00:17 2002

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.