Re: svn_wc__status2_from_3 does not copy locked info

2022-09-04 Thread Daniel Sahlberg
Den lör 3 sep. 2022 kl 08:31 skrev Barry : > > > > On 2 Sep 2022, at 15:09, Nathan Hartman > wrote: > > > >  > >> > >> On Mon, Aug 29, 2022 at 5:36 AM Barry Scott > wrote: > >> I had a pysvn user report that they cannot detect that a wc is locked. > >> > >> What I found is that I get that info

Re: svn_wc__status2_from_3 does not copy locked info

2022-09-02 Thread Barry
> On 2 Sep 2022, at 15:09, Nathan Hartman wrote: > >  >> >> On Mon, Aug 29, 2022 at 5:36 AM Barry Scott wrote: >> I had a pysvn user report that they cannot detect that a wc is locked. >> >> What I found is that I get that info and indeed locked == 0. >> >> This is because there is no code

Re: svn_wc__status2_from_3 does not copy locked info

2022-09-02 Thread Nathan Hartman
> On Mon, Aug 29, 2022 at 5:36 AM Barry Scott wrote: > I had a pysvn user report that they cannot detect that a wc is locked. > > What I found is that I get that info and indeed locked == 0. > > This is because there is no code in svn_wc__status2_from_3 to > copy locked value from old_status->lock

Re: svn_wc__status2_from_3 does not copy locked info

2022-08-29 Thread Barry Scott
> On 29 Aug 2022, at 14:18, Nathan Hartman wrote: > > On Mon, Aug 29, 2022 at 5:36 AM Barry Scott wrote: >> >> I had a pysvn user report that they cannot detect that a wc is locked. >> >> What I found is that I get that info and indeed locked == 0. >> >> This is because there is no code in

Re: svn_wc__status2_from_3 does not copy locked info

2022-08-29 Thread Nathan Hartman
On Mon, Aug 29, 2022 at 5:36 AM Barry Scott wrote: > > I had a pysvn user report that they cannot detect that a wc is locked. > > What I found is that I get that info and indeed locked == 0. > > This is because there is no code in svn_wc__status2_from_3 to > copy locked value from old_status->lock