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/14 12:56:10 UTC

[GitHub] sling pull request #202: SLING-6592 introduce "Content" interface instead of...

GitHub user stefanseifert opened a pull request:

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

    SLING-6592 introduce "Content" interface instead of nested maps

    

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

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

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

    https://github.com/apache/sling/pull/202.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 #202
    
----
commit 6092c10b1e720d3c05f53e9307808e271748dd00
Author: sseifert <ss...@pro-vision.de>
Date:   2017-03-14T12:49:20Z

    SLING-6592 introduce "Content" interface instead of nested maps

----


---
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 #202: SLING-6592 introduce "Content" interface instead of...

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

Github user stefanseifert closed the pull request at:

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


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