Re: [PATCH][MERGE-TRACKING] New function to create a mergeinfo hash out of a single path and single merge-range

> Current usage -- at least in libsvn_client's merging code, and some of
> mergeinfo.c -- has primarily been to either stack-allocate the
> svn_merge_range_t (using syntax like "r = {3, 7};"), or call
> svn_merge_range_dup().
>
>

Have seen it.
Atlast could find heap allocated 'svn_merge_range_t' in
subversion/libsvn_fs_util/merge_info_index.c :parse_mergeinfo_from_db.

With regards
Kamesh Jayachandran

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 05:45:15 2006