You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by stefanseifert <gi...@git.apache.org> on 2017/03/16 15:35:45 UTC

[GitHub] sling pull request #203: SLING-6592 switch to stream-based API for ContentPa...

GitHub user stefanseifert opened a pull request:

    https://github.com/apache/sling/pull/203

    SLING-6592 switch to stream-based API for ContentParser

    

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

    $ git pull https://github.com/stefanseifert/sling feature/SLING-6592-contentparser-stream-api

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

    https://github.com/apache/sling/pull/203.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 #203
    
----
commit 54159e8cba118cfa9df109e4e7fea6ce6ce1a55e
Author: sseifert <ss...@pro-vision.de>
Date:   2017-03-16T15:28:18Z

    SLING-6592 switch to stream-based API for ContentParser

----


---
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] sling pull request #203: SLING-6592 switch to stream-based API for ContentPa...

Posted by stefanseifert <gi...@git.apache.org>.

Github user stefanseifert closed the pull request at:

    https://github.com/apache/sling/pull/203


---
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.
---