[Insight-developers] First commit to ITK

[Bill Lorensen]

Yes, there is a DOC: prefix. The commit check requires at least one of
the following:

BUG:   - a change made to fix a runtime issue
            (crash, segmentation fault, exception, or incorrect
result,   COMP:  - a fix for a compilation issue, error or warning,
DOC:   - a change to the documentation,
ENH:   - new functionality added to the project,
PERF:  - a performance improvement,
STYLE: - a change that does not impact the logic or execution of the
            code. (improve coding style, comments).

On Thu, Feb 25, 2010 at 12:44 AM, Emmanuel Christophe
<emmanuel.christophe at gmail.com> wrote:
> Hi,
>
> In order to get familiar with the contribution process to ITK, I'm
> starting with a few corrections in the doxygen comments, correcting
> some:
> "reached end of file while inside a ** block" that causes some files
> not to appear in the class list, changing some /class into \class etc.
>
> This doesn't touch a single line of active code and all tests still
> run perfectly fine.
>
> However, I'm new to cvs (but familiar with svn and mercurial) so I've
> read some documentation. Is there anything I should know before
> attempting my first commit?
>
> Is a "DOC:" prefix suitable for the commit message?
>
> Best regards,
> Emmanuel
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
>