[GitHub] sling-site issue #2: Update manipulating-content-the-slingpostservlet-servle...

2017-10-06 Thread bdelacretaz
Github user bdelacretaz commented on the issue:

https://github.com/apache/sling-site/pull/2
  
The proposed changes look good to me in principle, thank you very much!
But do we have tests of those features? I don't remember the details off 
the top of my head and I'd like to make sure those details are correct. Or 
maybe have less details in the docs and point to those tests for the details.


---


[GitHub] sling-site pull request #1: TODO does commit to github work?

2017-09-29 Thread bdelacretaz
Github user bdelacretaz closed the pull request at:

https://github.com/apache/sling-site/pull/1


---


[GitHub] sling-site issue #1: TODO does commit to github work?

2017-09-29 Thread bdelacretaz
Github user bdelacretaz commented on the issue:

https://github.com/apache/sling-site/pull/1
  
Looks like we need to move to gitbox to be able to merge PRs from github, 
will look at that.


---


[GitHub] sling-site pull request #1: TODO does commit to github work?

2017-09-29 Thread bdelacretaz
GitHub user bdelacretaz opened a pull request:

https://github.com/apache/sling-site/pull/1

TODO does commit to github work?



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

$ git pull https://github.com/bdelacretaz/sling-site patch-1

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

https://github.com/apache/sling-site/pull/1.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 #1


commit 25e4d7310beed7369c93bc915b20f89ebf469f58
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2017-09-29T09:00:02Z

TODO does commit to github work?




---


[GitHub] sling pull request #242: SLING-6422: add to Nitin's patch a comparison that ...

2017-06-13 Thread bdelacretaz
GitHub user bdelacretaz opened a pull request:

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

SLING-6422: add to Nitin's patch a comparison that ignores ordering of 
restrictions



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

$ git pull https://github.com/bdelacretaz/sling SLING-6422

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

https://github.com/apache/sling/pull/242.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 #242


commit 4aa930056d48655995629b9253edd1bd394f7ecb
Author: Nitin Nizhawan <nitin.nizha...@gmail.com>
Date:   2017-05-16T11:01:56Z

SLING-6422, Allow for specifying oak restrictions with repoinit

   - Interpret parsed restriction clauses from repoinit

commit be2e488e33b01cf7fde54643e86489da47510d4a
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2017-06-13T11:58:40Z

Merge remote-tracking branch 'nitin/nnizhawa/SLING_6422ApplyRestrictionsV3' 
into SLING-6422

commit 8a3c4869a9416ee16cf441dd3babf85de6c9d73f
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2017-06-13T12:44:59Z

SLING-6422 - compare arrays regardless of their ordering




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


[GitHub] sling pull request #181: Issue/sling 5135

2016-10-11 Thread bdelacretaz
Github user bdelacretaz closed the pull request at:

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


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


[GitHub] sling pull request #181: Issue/sling 5135

2016-10-11 Thread bdelacretaz
GitHub user bdelacretaz opened a pull request:

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

Issue/sling 5135

Ready to commit this

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

$ git pull https://github.com/bdelacretaz/sling issue/SLING-5135

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

https://github.com/apache/sling/pull/181.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 #181


commit fe8f9559bda6ba5a05c01bba6a85e640fb8ac143
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2016-10-10T12:44:15Z

SLING-5135 - whitelist works for both loginAdministrative and 
getAdministrativeResourceResolver

commit 72d87914e4979368dbf15b49634b9d4eee71687c
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2016-10-10T12:45:00Z

SLING-5135 - disable one test that fails since updating to latest 
snapshots. Apparently unrelated to whitelist implementation.

commit 11deaf70fe81c2f8529143c1a348792d692b5624
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2016-10-10T12:45:47Z

SLING-5135 - update to latest snapshots to include login admin whitelist. 
Causes some other tests to fail

commit e131df5d34fdb61f0adf15749c4dbcfb63397270
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2016-10-10T13:42:20Z

SLING-5135 - test passes now that missing default login admin whitelistings 
have been added

commit eec9d8791d3c6da65d57df7129b6e9fa051b792b
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2016-10-11T12:09:07Z

MapEntries: add calling bundle info

commit 448a3fa4b729320008357445bb6b4a8f35a9edae
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Date:   2016-10-11T14:16:23Z

Fix get property bug




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