> -----Original Message-----
> From: Mark Phippard [mailto:markphip_at_gmail.com]
> Sent: woensdag 26 oktober 2011 14:15
> To: Bert Huijben
> Cc: Hyrum K Wright; dev_at_subversion.apache.org
> Subject: Re: Breakage in Status API
> On Wed, Oct 26, 2011 at 7:58 AM, Bert Huijben <bert_at_qqmail.nl> wrote:
> >> This workaround turns out to be not so perfect. Have you had a chance
> >> to look at this problem in the API?
> > I spend some time creating a test framework for comparing behavior, but
> > I found was a complete different issue.
> > In Subversion 1.6 status is reported as text_status and property_status,
> > while Subversion 1.7 reports status as node_status, text_status and
> > property_status.
> > The compatibility code in libsvn_client and libsvn_wc automatically
> > transforms the more complete status back to the old format (where node
> > status overwrites text status) while the code in javahl just ignores
> > node_status.
> Let me repeat it back to see if I understand.
> 1) The status API changed in 1.7 to report 3 statuses back
> - Since this was missed in JavaHL we will need to rev this in 1.8 so
> that JavaHL reports the 3 statuses.
I don't know about the JavaHL compatibility guarantees; maybe we can still
> 2) In libsvn_client where we need to maintain backwards compat the 3
> statuses are turned back into the values they would have had with the
> old 2 statuses.
> - The C++ part of JavaHL did NOT make the same backwards compat
> change. So this is something needs to be fixed for 1.7.x and should
> be possible to fix?
This should at least be done for the tigris package. For the apache package
we should either fix this in the same way as for tigris or add the new
Received on 2011-10-26 14:19:51 CEST