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

Re: Property values for boolean properties.

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-06-19 18:32:04 CEST

"Mark Phippard" <markphip@gmail.com> writes:
> Ben Collins-Sussman writes:
>> I like this idea of throwing in an extra warning. But I feel like I
>> missed something in Karl's original post. Karl brings up this whole
>> subject as if it were a de-facto truth that this potential UI
>> confusion is a serious problem... but is there really a problem here?
>> In all my years, I've never heard of anyone being bitten by this.

Uh, I'm pretty sure I've fielded the question in #svn before, and in
person with users, but it's only anecdotal evidence. I couldn't tell
you how often the confusion happens.

> I have the same reaction as Ben. This all sounds OK, but I have
> *never* seen this problem come up on the users@ list. I have also
> never heard of people using "on" as the prop value when setting the
> property.

Well, considering that's what most examples use (both in the book and
in some popular training slides), and it's the value I usually
use... I don't know how common "on" is, but I wouldn't be surprised if
it's the most common value.

Are you sure you've never seen this come up on users@? Again, I can't
point to the post, but it doesn't feel like it's coming out of nowhere
to me. I made my post because I felt like I was stumbling into the
question _again_, not because it just occurred to me for the first time.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 19 18:32:05 2007

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.