[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: svn status API and missing switched flag

From: Bert Huijben <bert_at_qqmail.nl>
Date: Mon, 12 Oct 2015 13:49:30 +0200

> -----Original Message-----
> From: Marc Strapetz [mailto:marc.strapetz_at_syntevo.com]
> Sent: maandag 12 oktober 2015 13:37
> To: Bert Huijben <bert_at_qqmail.nl>; dev_at_subversion.apache.org
> Subject: Re: svn status API and missing switched flag
>

> >
> > The old behavior makes sense if you think as the 'S' as switched against the
> ancestor... If you are not looking at an ancestor it can't be switched.
> >
> > If you see the behavior in 1.7, 1.8 or 1.9 then I agree that the api should at
> least provide switched information.
>
> I see this behavior with SVN 1.9.2.

I already reproduced the behavior, but thanks for confirming.

I'm looking what the options are here... It looks like it was an explicit api decision for the status walker. (The single status result api does provide the switched flag!)

Just adding the flag as simple fix would make the status much slower on a single directory without recursion. Every db transaction counts in this performance critical scenario. And as this was implemented explicitly this way for wc-ng we really have an api change at hand.

It is not that it was mostly undefined behavior as before 1.7.

        Bert
Received on 2015-10-12 13:49:46 CEST

This is an archived mail posted to the Subversion Dev mailing list.