Let's continue the discussion on dev@. [Moved from users@]
Ivan, would you like to write a regression test for this? See
subversion/tests/cmdline/info_tests.py.
Cheers,
Daniel
P.S. Nathan, are you aware of this syntax? — «svn log --diff -x-wp -c r1823327»
Nathan Hartman wrote on Fri, Nov 22
On Tue, Nov 19, 2019 at 12:03 AM Nathan Hartman
wrote:
>
> On Mon, Nov 18, 2019 at 4:53 AM Иван Селин
wrote:
>>
>> Hi!
>>
>> I think I've found a bug in subversion client. Setup is as follows:
>> 1. Create directory with a file in it — commit 1
>> 2. Replace directory with other file — commit 2
>
Hi, Nathan! Thanks for your reply. If you need anything else, I can provide more information to help debug the problem. Regards,Ivan. 19.11.2019, 08:04, "Nathan Hartman" :On Mon, Nov 18, 2019 at 4:53 AM Иван Селин wrote:Hi! I think I've found a bug in subversion client.
Hi, Eric! I think svn log -v is correct as it shows that /dir in commit 2 was replaced, i.e. removed and added: $ svn log -v file://$repo/dirr2 | ivanselin | 2019-11-19 08:34:37 +0300 (Tue, 19 Nov 2019) | 1 lineChanged paths:
On Mon, Nov 18, 2019 at 4:53 AM Иван Селин wrote:
> Hi!
>
> I think I've found a bug in subversion client. Setup is as follows:
> 1. Create directory with a file in it — commit 1
> 2. Replace directory with other file — commit 2
> 3. Call "svn info dir/file@1" — it should give information about d
Interesting.
It appears that svn ls of "dir@1" works fine. As does svn cat of "dir/file@1".
svn proplist of "dir/file@1" appears to work as well.
svn log -v appears to be incomplete, as it shows "dir" removed, but not
also added in the revision.
svn info fails, as you note.
Looks like a bug to