GitHub user RAbraham opened a pull request:
https://github.com/apache/spark/pull/1666
[SPARK-2735][Documentation] Remove deprecation warning in 'jekyll build'
for pygments
The following warning was corrected which shows up when one does 'jekyll
build' in the docs folder
"Deprecation: The 'pygments' configuration option has been renamed to
'highlighter'. Please update your config file accordingly. The allowed values
are 'rouge', 'pygments' or null."
Reference:https://github.com/mmistakes/hpstr-jekyll-theme/issues/25
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RAbraham/spark master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/1666.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 #1666
----
commit afd583dd1dd61ce91ed055d2e12e20dbc9d58286
Author: Rajiv Abraham <[email protected]>
Date: 2014-07-30T15:59:46Z
[SPARK-2735][Documentation] Remove deprecation warning in 'jekyll build'
for pygments
The following warning was corrected
"Deprecation: The 'pygments' configuration option has been renamed to
'highlighter'. Please update your config file accordingly. The allowed values
are 'rouge', 'pygments' or null."
Reference:https://github.com/mmistakes/hpstr-jekyll-theme/issues/25
commit 56957d2704176f2cf5f92d50216875c9979b87fc
Author: Rajiv Abraham <[email protected]>
Date: 2014-07-30T18:44:27Z
Merged [SPARK-2735][Documentation] Remove deprecation warning in 'jekyll
build' for pygments
The following warning was corrected
"Deprecation: The 'pygments' configuration option has been renamed to
'highlighter'. Please update your config file accordingly. The allowed values
are 'rouge', 'pygments' or null."
Reference:https://github.com/mmistakes/hpstr-jekyll-theme/issues/25
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
