RE: RE: RE: RE: RE: RE: Communication of LOCKS and CHANGES

> -----Original Message-----
> From: Reedick, Andrew [mailto:jr9445@ATT.COM]
> Sent: Wednesday, November 21, 2007 1:30 PM
> To: Harvey, Edward; users@subversion.tigris.org
> Subject: RE: RE: RE: RE: RE: Communication of LOCKS and CHANGES

> > -----Original Message-----
> > From: Harvey, Edward [mailto:Edward.Harvey@patni.com]
> > Sent: Wednesday, November 21, 2007 12:33 PM
> > To: users@subversion.tigris.org
> > Subject: RE: RE: RE: RE: Communication of LOCKS and CHANGES
> >
> > I'm really talking about something new.

>
>
> Hrmm... I sense a bit of a culture clash going on. The SVN
> client and any command line shell can already do what you
> ask. Just run 'svn status -u > status.txt' and *poof* you
> have your cached information.
> You can even script it to do 'svn info' and diffs on the updates.
>
> So it's not a new feature being asked for, instead, a better
> way of presenting the data is desired. GUI clients should

Indeed, that is exactly what I am suggesting. By cacheing the results
of a server query in a local file of standard format, GUI clients can
create a means to show that information in a consistant fashion. That
part does not exist now. That is what I am saying SHOULD exist.

> already be able to do something pretty with that information
> with the current version of SVN. This sounds more like a
> request better handled by clients like TortoiseSVN.

With that assertion, it falls on each GUI client to unilaterally create
their own means to cache and display the data. It also means they have
to use two separate operations behind the scene to get the data (two
calls to the server, twice the chattiness). Worse, developers using two
clients together have two caches to update. Not a good idea, so no, it
is not better handled by clients like TortoiseSVN. That is exactly who
should NOT handle it. Tortoise should make use of the cached data
available to it.

--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org