Hi Johan. As I know now there was networking problems with datacenter that
hosts svn repository I worked with. Also I see similar report in this
mailing list so I came to conclusion that this is a key condition for the
bug. But I will report to the TortoiseSVN mailing list as well.
Thanks.
пн, 3
On Wed, Jul 29, 2015 at 3:54 PM, Илья Денисов wrote:
> Hello, everyone. I've got an exception.
> Steps I made:
> * Open trunk history
> * Search for specific commit by typing bug tracker id in filtration bar at
> the top
> * Fetch more commits with "Next 100" button until I saw the commit
> * Open
Hello, everyone. I've got an exception.
Steps I made:
* Open trunk history
* Search for specific commit by typing bug tracker id in filtration bar at
the top
* Fetch more commits with "Next 100" button until I saw the commit
* Open some of the commited files with double click
* Close all opened vie
I get the assertion below when I do TortoiseSVN\Check for modifications on
a WC that contains a folder with file externals. I have no conclusive
proof that the file externals are the cause of the problem, but the fact
that the assertion deals with mis-matched repo id's strongly suggests
that
> -Original Message-
> From: Stefan Küng [mailto:tortoise...@gmail.com]
> Sent: maandag 17 oktober 2011 21:28
> To: Mark Phippard
> Cc: users@subversion.apache.org
> Subject: Re: TortoiseSVN exception dialog improvements?
>
> On 17.10.2011 19:46, Mark Phippard wr
On 17.10.2011 19:46, Mark Phippard wrote:
I wonder if the TortoiseSVN team could create a link to a Google
search for the error code on the dialog where they ask the user to
report the problem? It could ask them to check that link first for
other reports of the same problem.
That might cut down
I wonder if the TortoiseSVN team could create a link to a Google
search for the error code on the dialog where they ask the user to
report the problem? It could ask them to check that link first for
other reports of the same problem.
That might cut down on the list spam and also get the user an a
