I've stumbled on a weird incostistency in Svn behavior.
I have a USB stick with 5 repositories in it. They all are organized
the same way as recommended in the Svn book: every repository
has its own "project root" directory, in which version control,
organizational dirs - "trunk", "branches" and "tags" are placed.
Behind them a source tree themselves goes.
So, with one of the repos and only it, this oddity appears.
Normally, when I do checkout a repo for getting a new working copy,
for example on another computer, I type:
Code:
>svn co file:///R:/Svn/Project1Root/trunk pr1
and it outputs, something like this:
Code:
A pr1\src
...
A pr1\src\source.c
Checked out revision 33554432.
But for one repo, the very same command:
Code:
>svn co file:///R:/Svn/osloader/trunk osl
results in a sightly different output:
Code:
A osl\arm64
...
A osl\fs.c
U osl
The last line is the difference: it reports, that the directory
"osl", we chose to place our working copy into, has been updated,
that's why 'U' in the
2nd column.
But why the same line doesn't appear
for the other repos? This behavior replicates no matter the differencies
in doing the checkout in regard of how the directory is being created - by you
via, say, mkdir or by Svn implicitly
or either you operate from its parent directory
or from it, that is even if you, being in the dir, will type:
Code:
>mkdir osl
>cd osl
>svn co file:///R:/Svn/osloader/trunk .
It still will report it like this:
Code:
A arm64
...
A fs.c
U .
Why this difference? Has anybody in this git ruled world stumbled upon
this or does know, why it happens or it's a Heisenbug? The Svn version
is 1.9.5 (r1770682).