Stefan Küng wrote:
> Thomas Hruska wrote:
>
>> Oh good. I'm not the only one seeing this happen. Whenever I report
>> a bug anymore, the devs get annoyed for whatever reason.
>
> Thanks for that comment.
>
> I only get annoyed by bug reports which are not reproducible. As long as
> I can't reproduce a bug, I can't fix it. And I hope you can imagine that
> this can get really annoying.
>
>> I'm seeing this mostly with directories and I've been able to repeat
>> the bug by having a modified file in a subdirectory and then adding a
>> new file in the main directory to SVN. When I do that, every icon
>> changes to a green checkmark...including the '.svn' subdirectory in
>> the main directory. Attached is a screenshot of what I mean. (I
>> blacked out critical segments and drew on the image to indicate what
>> the problems are).
>
> Just tried that. And I still can't reproduce that. (Yes, that means I'm
> getting annoyed - but what would you do if you were in my position?).
>
>> This bug seems to show up more often on removable media (e.g. USB
>> thumbdrives) and it fixed itself one time on my main hard drive but
>> only after I checked in my changes and it took about 2 minutes to get
>> around to fixing itself. I haven't checked in the changes shown in
>> the attached image since I upgraded to 1.4.0, but I have rebooted a
>> couple times (due to Windows updates). So, this means the working
>> copy is using the old 1.3.x format. It may correct itself when I
>> check in my work, but that's a week away.
>
> Does it happen if you check out a fresh working copy with version 1.4.0
> too?
I've been thinking this is just a migration issue with working copies
from 1.3.x, which is why I haven't reported it. In other words, it is
probably my fault for upgrading to 1.4.0 and then using 1.4.0 to make
changes on a 1.3.x working copy and then complaining about it not
working as expected.
I suspect that to reproduce, you would have to downgrade to 1.3.5, then
check out a working copy, make some changes, then upgrade to 1.4.0, make
some new changes, and then the bug will show up. I've gotten it to show
up fairly consistently. It seemed to go away in one of my wc's a couple
minutes after doing a SVN Commit. So I went on a SVN Update rampage
except where I'm currently working and haven't seen the problem show up
anywhere that I've done SVN Update.
I'll be able to tell if the problem goes away once I do my check in
later this week.
--
Thomas Hruska
CubicleSoft President
Ph: 517-803-4197
Safe C++ Design Principles (First Edition)
Learn how to write memory leak-free, secure,
stable, portable, and user-friendly software.
Learn more and view a sample chapter:
http://www.CubicleSoft.com/SafeCPPDesign/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 2 18:49:05 2006