Markus Schaber wrote on Fri, May 13, 2011 at 11:20:11 +0200:
> Hi,
>
> What is the safest future-compatible way to check for an incompatible /
> unknown working copy format which was written by a future subversion
> version? (e. G. WC-NG by SVN 1.7?)
>
> My idea was to run status with depth=empty
Markus Schaber wrote on Fri, May 13, 2011 at 11:20:11 +0200:
> Hi,
>
> What is the safest future-compatible way to check for an incompatible /
> unknown working copy format which was written by a future subversion
> version? (e. G. WC-NG by SVN 1.7?)
>
> My idea was to run status with depth=empty
2011/5/13 Markus Schaber :
> Hi,
>
> What is the safest future-compatible way to check for an incompatible /
> unknown working copy format which was written by a future subversion
> version? (e. G. WC-NG by SVN 1.7?)
>
In the change log for Subversion 1.6 [1] there is the following line for 1.6.9.
On 5/13/11 7:30 AM, Erik Huelsmann wrote:
What is the safest future-compatible way to check for an incompatible /
unknown working copy format which was written by a future subversion
version? (e. G. WC-NG by SVN 1.7?)
My idea was to run status with depth=empty on the workingcopy root, and
che
Hi Markus,
On Fri, May 13, 2011 at 11:20 AM, Markus Schaber
wrote:
> Hi,
>
> What is the safest future-compatible way to check for an incompatible /
> unknown working copy format which was written by a future subversion
> version? (e. G. WC-NG by SVN 1.7?)
>
> My idea was to run status with depth
