On Thu, 08 Nov 2007, pburba@tigris.org wrote:
...
> --- trunk/subversion/tests/libsvn_subr/mergeinfo-test.c (original)
> +++ trunk/subversion/tests/libsvn_subr/mergeinfo-test.c Thu Nov 8 09:08:34 2007
...
> -#define NBR_MERGEINFO_VALS 3
> +#define NBR_MERGEINFO_VALS 5
> /* Valid mergeinfo values. */
> static const char * const mergeinfo_vals[NBR_MERGEINFO_VALS] =
> {
> "/trunk:1",
> "/trunk/foo:1-6",
> - "/trunk: 5,7-9,10,11,13,14"
> + "/trunk: 5,7-9,10,11,13,14",
> + "/trunk: 3-10,11*,13,14",
> + "/branch: 1,2-18*,33*"
> + /* ### Should svn_mergeinfo_parse() handle unordered
> + ### but otherwise valid input strings like this?
> + ### Currently this fails.
> + /* "/trunk: 7-9,5,10,14,13,11" */
> };
svn_mergeinfo_parse() was never intended to handle unordered
rangelists. Its doc string doesn't currently reflect this, but
probably should.
- application/pgp-signature attachment: stored
Received on Thu Nov 8 19:45:38 2007