[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: BUG: FixCaseRenames happens too early?

From: Antony Bartlett <akb_at_akb.me.uk>
Date: Tue, 27 Oct 2015 11:56:43 -0700 (PDT)

> On 16/10/2015 22:51, Antony Bartlett wrote:
> > I’m sure this has already occurred to you, but just so I understand – why not do the case-fix in both places? It does seems a shame to click ‘OK’ to two files being committed, and only commit one file. The commit dialog performs admirably in the difficult circumstance in which I leave the commit dialog open and edit files – never a good idea, but I’ve never had a problem with doing it except in this peculiar case-sensitivity circumstance.
> Have you tried pressing F5 when returning to the commit window after making your external change? This is the only way to eg. detect changes to files not listed in the original commit.

Yep you're right, Gavin - there's no problem with the commit if I press F5 at the appropriate point. That's not really the point though, which is about the commit not being atomic in my original scenario. If, on the other hand, I make "changes to files not listed in the original commit" and press OK, then the commit dialog does exactly what it says it is going to, and it is completely my own stupid fault for not pressing F5 if I wanted those other changes committed - I hope I've made that clear enough and you understand the difference?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-10-27 19:56:51 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.