You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by dhalperi <gi...@git.apache.org> on 2016/11/03 17:15:26 UTC
[GitHub] incubator-beam-site pull request #60: add a symlink to current Javadoc
GitHub user dhalperi opened a pull request:
https://github.com/apache/incubator-beam-site/pull/60
add a symlink to current Javadoc
R: @francesperry @davorbonaci @evilsoapbox
Note this is a filesystem-level symlink; in practice it appears that Jekyll will generate two copies of the content rather than a HTTP 301/302 to redirect. I figured symlink is easier to maintain than a custom 302 page, so this is the lesser evil.
But there may be a better way to do this.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dhalperi/incubator-beam-site symlink-javadoc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam-site/pull/60.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 #60
----
commit 80b09ccefd0212a4b006a3dcc3527987a1f9ef64
Author: Dan Halperin <dh...@google.com>
Date: 2016-11-03T17:13:01Z
add a symlink to current 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] incubator-beam-site pull request #60: add a symlink to current Javadoc
Posted by dhalperi <gi...@git.apache.org>.
Github user dhalperi closed the pull request at:
https://github.com/apache/incubator-beam-site/pull/60
---
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.
---