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

Re: Question regarding svn_ra_do_update and delta data

From: <kfogel_at_collab.net>
Date: 2005-12-09 20:35:48 CET

"Ph. Marek" <philipp.marek@bmlv.gv.at> writes:
> I've stumbled upon a problem and would like to get some hints.
>
>
> The problem is:
> - I've local files, which I knew at which version they've been when checking
> out.
> - They are changed.
> - I have no original full-text available.
> - I'd like to update them.
>
>
> Currently I just do an svn_ra_do_update() and receive the tree diffs as usual
> - new files, deleted files, and so on.
> But if a file has changed locally *and* in the repository - what should I do?
> I tried to give /dev/null or an empty stringbuf as source for
> svn_txdelta_apply; but that gives me "Delta source ended unexpectedly".

I don't understand what you mean by "I tried to give /dev/null or an
empty stringbuf as source for svn_txdelta_apply". You're calling
svn_ra_do_update(), a function which thinks its updating a working
copy, and which will try to report that working copy's state to the
server in order to get an efficient update response back. Where did
you have an opportunity to even be calling svn_txdelta_apply()? You
don't drive the editor; the RA layer does.

So, I think I'd need a lot more detail to understand what you did
above :-).

> Is there a way to receive text updates in full, ie. not as a diff, for some
> files in an update-operation?

Well, can you use the reporter handed back to you by
svn_ra_do_update() to tell the server that you don't those files?

-Karl

-- 
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 9 22:01:57 2005

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.