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

Re: bring on your concerns about svn:hold, please

From: Konstantin Kolinko <knst.kolinko_at_gmail.com>
Date: Tue, 23 Aug 2011 14:09:59 +0400

2011/8/22 Stefan Küng <tortoisesvn_at_gmail.com>:
> On 22.08.2011 18:51, Neels J Hofmeyr wrote:
>>> Since TortoiseSVN has had this feature for a long time, it would
>>> be interesting to know what kind of edge cases people have raised with
>>> the
>>> feature.  Has anyone asked that these files not be updated or merged?
>> I've asked, but only on this list... good point, I should ask tortoise
>> devs
>> directly. (But their changelist is called "ignore-on-commit", so it's
>> pretty
>> clear what it does, I guess.)
> Apart from a few bugs in our code, we haven't had any issues with that
> special changelist. At least users haven't reported any.
> The bugs we had were related to having files in that changelist initially
> checked for commit when the commit dialog came up.
> Stefan

One thing I miss with "ignore-on-commit" is that I actually want all
changelists to behave this way: to be unselected by default.

I usually use change lists to mark some work in progress. When
committing I have to start with unselecting all, then I usually select
the non-in-changelist items (they are grouped in TortoiseSVN as well)
or the changelist I want to commit.

If anyone wants to keep the current behaviour where only
"ignore-on-commit" is special, it could be customizable, e.g.
configure it to ignore all "ignore-*" or "WIP-*" lists, or "*".

Best regards,
Konstantin Kolinko
Received on 2011-08-23 12:10:46 CEST

This is an archived mail posted to the Subversion Dev mailing list.

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