apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From PramodSSImmaneni <...@git.apache.org>
Subject [GitHub] apex-malhar pull request #350: Added development best practices
Date Tue, 26 Jul 2016 06:54:13 GMT
GitHub user PramodSSImmaneni opened a pull request:

    https://github.com/apache/apex-malhar/pull/350

    Added development best practices

    @sashadt please review and merge
    
    This is from the discussion in the mailing list below. The document was available for
review by everyone. There were comments from different folks and they were addressed.
    
    https://www.mail-archive.com/dev%40apex.apache.org/msg01027.html

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

    $ git pull https://github.com/PramodSSImmaneni/apex-malhar malhar-contribution

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

    https://github.com/apache/apex-malhar/pull/350.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 #350
    
----
commit 656b0df6c4c3559ac2028f05d830c1caf8b6e0e9
Author: Pramod Immaneni <pramod@datatorrent.com>
Date:   2016-07-26T06:43:42Z

    Added development best practices

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message