Talk:Update a configuration file: Difference between revisions
Content added Content deleted
(Created page with "This task spec seems needlessly complex. For example "In commenting out an option, any duplicates should also become commented." does this mean that changes should be made by co...") |
(→Task spec issues: I think I know why it's like this…) |
||
| Line 1: | Line 1: | ||
== Task spec issues == |
|||
This task spec seems needlessly complex. For example "In commenting out an option, any duplicates should also become commented." does this mean that changes should be made by commenting out the old option instance and adding a new line? If not, how can we satisfy this requirement in the task implementation? --[[User:Rdm|Rdm]] 11:33, 20 May 2011 (UTC) |
This task spec seems needlessly complex. For example "In commenting out an option, any duplicates should also become commented." does this mean that changes should be made by commenting out the old option instance and adding a new line? If not, how can we satisfy this requirement in the task implementation? --[[User:Rdm|Rdm]] 11:33, 20 May 2011 (UTC) |
||
: He's trying to get us to duplicate the (over-complex IMO) functionality that he put into his implementation of this task. –[[User:Dkf|Donal Fellows]] 13:38, 20 May 2011 (UTC) |
|||
Revision as of 13:38, 20 May 2011
Task spec issues
This task spec seems needlessly complex. For example "In commenting out an option, any duplicates should also become commented." does this mean that changes should be made by commenting out the old option instance and adding a new line? If not, how can we satisfy this requirement in the task implementation? --Rdm 11:33, 20 May 2011 (UTC)
- He's trying to get us to duplicate the (over-complex IMO) functionality that he put into his implementation of this task. –Donal Fellows 13:38, 20 May 2011 (UTC)