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

use of commit_items param in svn_client__do_commit()

From: Madan U Sreenivasan <madan_at_collab.net>
Date: 2006-11-15 15:20:39 CET


    I have a situation while implementing wc to repos copy for
merge-tracking. I decided to mail the list, since breaking my head over it
didnt turn out any useful choices.

The situation:
   svn_client__do_commit() function uses the do_item_commit() function to
check-in changes from the working copy. But it does not use the whole of
the commit_items array (an array of svn_client_commit_item2_t). Instead
only the paths from the commit_items array are passed to do_item_commit().

My problem is:

   During a wc to repos copy, we need to update the mergeinfo of the target
(in the repos) with the svn:mergeinfo propery computed. This propchange
will not be present in the wc (because it is a wc to repos cp). So, I
envision passing these property changes as part of the commit_items array
(wcprop member), expecting this to be taken care of by the
svn_client__do_commit() function(how? By taking into consideration the
mergeinfo change in addition to whatever changes are present in the wc to
be committed). Is this the right thing to do? Can we change the
svn_client__do_commit() function to handle this?

    Is this a one off case? I dont think so. If it were, passing an array
of svn_client_commit_item2_t into svn_client__do_commit() might be an
overallkill, when the function only uses the paths in the array.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 15 15:20:49 2006

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