You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by alopresto <gi...@git.apache.org> on 2016/04/26 18:58:33 UTC
[GitHub] nifi pull request: Fixed typo in ScryptCipherProviderGroovyTest Ja...
GitHub user alopresto opened a pull request:
https://github.com/apache/nifi/pull/380
Fixed typo in ScryptCipherProviderGroovyTest Javadoc.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alopresto/nifi NIFI-1813
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/380.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 #380
----
commit 9b8fc3bb500bb3f4bd9275def7987aac7d858f10
Author: Andy LoPresto <al...@apache.org>
Date: 2016-04-26T01:32:45Z
Fixed typo in ScryptCipherProviderGroovyTest Javadoc.
----
---
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.
---
[GitHub] nifi pull request: Fixed typo in ScryptCipherProviderGroovyTest Ja...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/380
---
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.
---
[GitHub] nifi pull request: Fixed typo in ScryptCipherProviderGroovyTest Ja...
Posted by apiri <gi...@git.apache.org>.
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/380#issuecomment-215201206
Changes look good, +1
---
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.
---