On Fri, Aug 02, 2002 at 10:09:58AM -0500, Brian Finley wrote: > General statement: > It won't always be possible for the person writing code to know when > others think it's worth a discussion.
Very true, and this is why I feel it necessary to point out such occurences. Now, for example, you know that at least one of us thinks renaming a config file is worth a discussion. > It's not always possible or > reasonable to have a discussion before writing code True that. Writing code w/o discussion is not something I have a problem with - I have many trees laying around where I worked out ideas prior to letting those trees rot. > > Therefore: > The commit list should be considered part of the discussion and written > code should be considered communication of the idea. This means that > any changes committed can be considered the start of an open discussion > about their value. A piece of code is worth a thousand words. :-) True - but since undoing a commit can be a significant barrier, it's easier to scream before hand. I'm a lot more uncomfortable w/ asking somewhat to remove their code then I am with suggesting it not be committed. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
