kameshj_at_tigris.org wrote:
> Author: kameshj
> Date: Tue Nov 4 05:46:50 2008
> New Revision: 34039
>
> Log:
> On issue-2897-take2 branch:
>
> * README.branch
> New file having the plan for this branch.
>
> Added:
> branches/issue-2897-take2/README.branch
>
> Added: branches/issue-2897-take2/README.branch
> URL: http://svn.collab.net/viewvc/svn/branches/issue-2897-take2/README.branch?pathrev=34039
> ==============================================================================
> --- /dev/null 00:00:00 1970 (empty, because file is newly added)
> +++ branches/issue-2897-take2/README.branch Tue Nov 4 05:46:50 2008 (r34039)
> @@ -0,0 +1,13 @@
> +This branch started with the motto of implementing issue-2897 branch
> +as per new state of backend storage schema.
> +
> +As of today(r34038) we have 'per commit mergeinfo_delta' implemented in bdb fs.
> +
> +In the subconf Julian has given a suggestion to compute the
> +'per commit mergeinfo_delta' using 'log -g client code' so
> +that one could try 'trunk svn merge --reintegrate' and
> +'issue-2897-take2 svn merge' compare and contrast easily.
> +
> +So I am going to implement 'svn_client__get_commit_and_merge_ranges'
> +using 'log -g' code as a proof of concept and port rest of client code
> +from issue-2897 branch.
We've had a number of requests for changes to the 'log -g' API, and while they
aren't going to happen before 1.6, I think they may be useful to keep in mind
for this work.
The biggest change, which is on my "I'll do it eventually" list, is to have the
receiver API return the fact that a merge occurred, but omit the actual merged
revisions. This would allow clients to decide if they want the merged revisions
and make repeated calls to the log API to get those merged revisions. I don't
how or if this impacts your work for issue 2897, but I thought I'd mention it.
-Hyrum
Received on 2008-11-04 15:49:34 CET