On 07/08/2011 12:25 PM, Stefan Küng wrote:
> On 08.07.2011 18:03, C. Michael Pilato wrote:
>> On 07/08/2011 11:47 AM, Bert Huijben wrote:
>>> (Stefan: I'll check if I can find where the regression occurred later
>>> this weekend)
>>
>> ... after filing a blocker issue in the tracker, of course. ;-)
On 08.07.2011 18:03, C. Michael Pilato wrote:
On 07/08/2011 11:47 AM, Bert Huijben wrote:
(Stefan: I'll check if I can find where the regression occurred later this
weekend)
... after filing a blocker issue in the tracker, of course. ;-)
Filed as issue 3954:
http://subversion.tigris.org/is
On 07/08/2011 11:47 AM, Bert Huijben wrote:
> (Stefan: I'll check if I can find where the regression occurred later this
> weekend)
... after filing a blocker issue in the tracker, of course. ;-)
--
C. Michael Pilato
CollabNet <> www.collab.net <> Distributed Development On Demand
s
> -Original Message-
> From: C. Michael Pilato [mailto:cmpil...@collab.net]
> Sent: vrijdag 8 juli 2011 17:40
> To: Stefan Küng
> Cc: Subversion Development
> Subject: Re: svn_client_status5 and depth_as_sticky
>
> On 07/08/2011 10:57 AM, S
On 08.07.2011 17:39, C. Michael Pilato wrote:
On 07/08/2011 10:57 AM, Stefan Küng wrote:
Hi,
svn_client_status5 has a parameter depth_as_sticky. According to the doc
string:
If depth_as_sticky is set and depth is not svn_depth_unknown, then the
status is calculated as if depth_is_sticky was pa
On 07/08/2011 10:57 AM, Stefan Küng wrote:
> Hi,
>
> svn_client_status5 has a parameter depth_as_sticky. According to the doc
> string:
>
> If depth_as_sticky is set and depth is not svn_depth_unknown, then the
> status is calculated as if depth_is_sticky was passed to an equivalent
> update comm
Hi,
svn_client_status5 has a parameter depth_as_sticky. According to the doc
string:
If depth_as_sticky is set and depth is not svn_depth_unknown, then the
status is calculated as if depth_is_sticky was passed to an equivalent
update command.
this should report *everything* there is, even
7 matches
Mail list logo
