On 18.03.2010 22:25, Adrian Buehlmann wrote:
>>> But why not implement dropping locked and readonly via HKCU in
>>> *TortoiseOverlays* in advance now? It would be an easy thing to
>>> copy/paste the code lines for dropping ignored/unversioned and adjust
>>> them to drop locked/readonly as well.
> I guess this is a "not yet" then. I guess not unless you have it
> implemented in the TSVN GUI.
> Makes sense from your point of view.
I've never held back anything in the overlays component just because it
wasn't implemented in TSVN yet.
But I do need something to test the changes in the overlays component
before I can make a release. And usually for that I'm using TSVN.
So if that's a problem for you, I'm sorry.
>> I've already changed the dropping order for you. Which is in favor or
>> THg but worse for TSVN.
> For which I am grateful, thank you.
> BTW, locking-related overlays are meaningless for *all* DVCS, so I bet
> it's a benefit for the git and bzr tortoises as well.
> The minor problem is that the change is bundled with a whole new
> dropping mechanism via HKCU, that can only be controlled from TortoisSVN
> dialogs currently.
And that is my fault?
All you have to do is to implement those options in THg before you ship
it with the new overlays component.
> Which makes it questionable for me to go back to using unversioned now.
How much time do you need to implement two checkboxes in your options
And how much time do you need to go back to an earlier version of the
Do the math.
> But I agree the other changes are beneficial for TortoiseHg. Thanks again.
>> I've implemented dropping the ignored/unversioned because that's what we
>> already had in TSVN (the settings).
>> I know you have to care for THg, but please keep it calm and don't
>> overreact about every little change.
>> This change isn't worse for THg than it was before. It's even much
>> better now.
> It is a drawback in the sense that we have no control over what is in
> the HKCU TortoiseOverlays drop settings currently from the TortoiseHg
> GUI. It is currently only controlled by TortoiseSVN settings GUI.
But in an unreleased version of TSVN. There's still plenty of time for
you until the next version of TSVN is released.
> And it was a surprising to see that being introduced (a new setting
> affecting all tortoises).
Why was this surprising?
If you hadn't checked the code, you wouldn't even have noticed it
because it wouldn't have affected your client at all.
> But as soon as the mechanism is implemented for unlocked and readonly
> too, it makes sense for us as well.
I may have this ready this weekend. But don't count on it.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-18 22:37:54 CET