GitHub user aledsage opened a pull request:

    https://github.com/apache/incubator-brooklyn/pull/318

    Fix NOTICE: remove config files

    These config files are based on the defaults shipped with the given 
projects,
    but just match snippets from the docs, and examples that are readily
    available on a myriad of blogs. Our template config files are similar
    to the default files, but unsurprisingly the defaults match docs and
    thus match what one would write for a basic deployment.
    
    See discussion on dev@brooklyn mailing list, subject: "Re: [VOTE] Release 
Apache Brooklyn 0.7.0-M2-incubating [rc0]"

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aledsage/incubator-brooklyn 
fix/notice-remove-config-files

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-brooklyn/pull/318.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #318
    
----
commit 26f5f7a2bd2eef6476480a875e72f92ee638f7f4
Author: Aled Sage <[email protected]>
Date:   2014-11-11T22:44:33Z

    Remove from NOTICE MariaDB/JBoss config files
    
    - These are based on the defaults shipped with the given projects, 
      but just match snippets from the docs, and examples that are readily 
      available on a myriad of blogs. Our template config files are similar 
      to the default files, but unsurprisingly the defaults match docs and 
      thus match what one would write for a basic deployment.

commit 66a89a7cb6d04bdd51479ac8b702ab2e771bd1c3
Author: Aled Sage <[email protected]>
Date:   2014-11-11T22:45:02Z

    Improve RAT exclusion wording for config files

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to