[Kc] editors and IDEs (was: May Meeting)
davidnicol at gmail.com
Thu May 8 12:34:39 PDT 2008
On Thu, May 8, 2008 at 1:50 PM, Eric Wilhelm <scratchcomputing at gmail.com> wrote:
> Well, David meant 'action', 'verb', or 'command' -- not 'property'.
I meant "thing you can type on the command line after 'svn [-options]'
and something happens other than you get told "unknown command / type
'svn help' for help"
so I guess I could have put "command" to be conform to svn. I didn't,
I used a piece of jargon, because I'm not whining about the lack of
that particular feature (a real-easy way to do smoething that is
not-that-difficult) but suggesting it as the best example I know of a
feature that will never get added to an open-source project maintained
by volunteers. Pondering that fact (well it is now possible that
someone will go and add it, just to ruin my little lecture) is what
led me to the list of three things that have to be in place before a
feature gets added to an open-source project maintained by volunteers.
The benefit of making the change has to be greater than the cost of
the workaround, to someone who has the skills to make the change.
adding an "ignore" command to svn fails the test, because anyone who
could add it would also be able to script an external tool to modify
the property directly, using the propset command.
back to work, everyone
More information about the kc