Hi,
On 11/27/05, Casper Hornstrup ch@csh-consult.dk wrote:
Well, the voting is about what the standard should be (e.g. for new files). It doesn't specify anything about what to do with the existing headers. They could be replaced over time for instance.
This is fine with me. I will be voting for C. Once we have a standard I am sure we can find some Janitor that would love to help out by standardising the source headers for all of the ReactOS code. As long as this would not effect code we regularly import from other projects its fine with me. Adding this to the code we have already forked and or will not be trying to re-sync with seems like a good idea. However we should not replace the existing license header in any third party code we fork, we should append our header if we make major additions.
-- Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo