> (I understand your "Thanks" as +1) > > > If there is agreement on CR 19, then there is the possibility of > > automatically reformatting the entire codebase. I think a single > > consistent style over all the code will improve development. For SVN > > histories, it sounds like the sooner this is done, the better. Perhaps a > > good opportunity would be immediately after 2.0.0? > > Automation (and application of "new style" to "old" code) was debated > (e.g. follow-ups of > http://lists.wald.intevation.org/pipermail/openvas-devel/2008-November/001075.html > and in IRC). > > So far, most people who commented that issue estimated that it brings more > difficulties than benefits and should not be done or only under special > circumstances.
I had looked through the mailing list discussion, at least. I guess I've taken the opinions too lightly. > > I think this discussion should be made indepent of CR#19. Yes, it's a separate, follow-on issue. > Maybe you want to open a new Change Request? Perhaps that should wait for the new year. _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
