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

Re: Bug reports / don't break locks by default

From: cpengr <cp.engr0_at_gmail.com>
Date: Thu, 1 Oct 2015 12:16:19 -0400

Also, we use svn locks here, so this has been bothersome for a while. I
always unchecked that box, and I don't think I've ever seen it not be
pre-checked since it was added, or since the cleanup dialog was revised
(whichever came later).
On Oct 1, 2015 11:46 AM, "cpengr" <cp.engr0_at_gmail.com> wrote:

> > If you uncheck it, it won't be pre-checked the next time you use the
> cleanup dialog.
>
> I just tried what you described. It remains pre-checked.
> On Oct 1, 2015 11:33 AM, "Stefan Küng" <tortoisesvn_at_gmail.com> wrote:
>
>> On 30.09.2015 23:58, cpengr wrote:
>> > In some recent version of tsvn, the default behavior in the cleanup
>> > dialog was changed to "Break locks" by default. This is bad behavior,
>> > and I'd like to file a bug report, but I don't have permission on
>> > sourceforge. How should I proceed?
>> >
>> > I'm using the latest, v1.9.2, 64-bit.
>>
>> The checkbox remembers the state last used. If you uncheck it, it won't
>> be pre-checked the next time you use the cleanup dialog.
>>
>> Stefan
>>
>> --
>> ___
>> oo // \\ "De Chelonian Mobile"
>> (_,\/ \_/ \ TortoiseSVN
>> \ \_/_\_/> The coolest interface to (Sub)version control
>> /_/ \_\ http://tortoisesvn.net
>>
>> ------------------------------------------------------
>>
>> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3140418
>>
>> To unsubscribe from this discussion, e-mail: [
>> users-unsubscribe_at_tortoisesvn.tigris.org].
>>
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3140435

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-10-01 18:16:28 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.