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

On Tue, 10 Oct 2006, Kamesh Jayachandran wrote:

> I would see it would be more useful to have the following,
> svn_range_create(start, end) which would have more use than this combo
> (svn_mergeinfo__make).

An svn_merge_range_t only contains two field, start and end (see
svn_types.h). Is there really enough value in adding a constructor
function for such a simple data type? (We already have an
svn_range_dup() API).

I was thinking of adding a svn_rangelist_create(start, end, pool) API,
which would add one range to a list, providing part of the
implementation for svn_mergeinfo__make(start, end, pool). However,
I'd be most influenced by a patch which shows where we'd actually use
these APIs.