Hi,
My copy of Project Monitor has decided to stop displaying any SVN log data,
not even from previous updates. All projects are still there but when I
click on any of them the main pane remains empty and status bar displays
"Waiting for monitoring thread to finish...".
I've rebooted the compu
It is a minor issue but causes some inconsistent user experience.
bugtraq:message is set to "ID=%BUGID%" in the whole repository so the
"Bug-ID / Issue-Nr:" editbox appears on the Commit Dialog.
When I select a recent message where the ID is set, this number is
automatically extracted from the m
This is a minor issue affecting the list behavior on Commit dialog.
Steps to reproduce:
1. set "svn:needs-lock" on a file
2. acquire lock on this file so it is not read-only anymore
3. make some changes to the content
4. open Commit dialog with this file
5. open context menu for th
I would like to propose a new condition for the /closeonend automation
parameter:
auto close if there are no changes at all (list is empty)
--
You received this message because you are subscribed to the Google Groups
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails
Thanks. That is kinda what I was figuring what I would have to do.
On Monday, February 19, 2018 at 8:35:27 AM UTC-5, Edward Prochak wrote:
>
>
>
> On Saturday, February 17, 2018 at 9:45:24 AM UTC-5, TC Mauldin wrote:
>>
>>
>>
>> On Friday, February 16, 2018 at 5:15:00 PM UTC-5, Edward Prochak wrot
On Thursday, February 22, 2018 at 9:30:45 AM UTC+1, Álvaro González wrote:
>
> Hi,
>
> My copy of Project Monitor has decided to stop displaying any SVN log
> data, not even from previous updates. All projects are still there but when
> I click on any of them the main pane remains empty and sta
That's actually expected: reading properties remotely is very slow, so in
the repo browser the properties are not read and therefore not used.
--
You received this message because you are subscribed to the Google Groups
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emai
That's not really feasible. For example if you run "update", even if there
are no file content updates, the working copy is still updated internally:
the revision to which it was updated is stored on the folder itself, so
there's still 'a change'.
--
You received this message because you are s
TMerge does not have the means to fetch files from a working copy,
especially not from a repository.
To make this work, we'd have to fetch and save all the possible files to a
temp location and then pass the full list to TMerge. Now imagine a commit
dialog with 200 changed files...
So no, that
