mesos git commit: Fixed incorrect glog link.

[me...@apache.org]

Repository: mesos
Updated Branches:
  refs/heads/master 839ba726e -> 1dd072738


Fixed incorrect glog link.

Review: https://reviews.apache.org/r/36422


Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/1dd07273
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/1dd07273
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/1dd07273

Branch: refs/heads/master
Commit: 1dd0727381e9e8602d3d9056757214968316b5fc
Parents: 839ba72
Author: haosdent huang <ha...@gmail.com>
Authored: Sat Jul 11 00:19:01 2015 -0700
Committer: Adam B <ad...@mesosphere.io>
Committed: Sat Jul 11 00:19:01 2015 -0700

----------------------------------------------------------------------
 docs/logging-and-debugging.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/1dd07273/docs/logging-and-debugging.md
----------------------------------------------------------------------
diff --git a/docs/logging-and-debugging.md b/docs/logging-and-debugging.md
index 1f037d6..6797d15 100644
--- a/docs/logging-and-debugging.md
+++ b/docs/logging-and-debugging.md
@@ -4,6 +4,6 @@ layout: documentation
 
 # Logging and Debugging
 
-Mesos uses the [Google Logging library](http://code.google.com/p/google-glog) and writes logs to `MESOS_HOME/logs` by default, where `MESOS_HOME` is the location where Mesos is installed. The log directory can be [configured](configuration.md) using the `log_dir` parameter.
+Mesos uses the [Google Logging library](https://github.com/google/glog) and writes logs to `MESOS_HOME/logs` by default, where `MESOS_HOME` is the location where Mesos is installed. The log directory can be [configured](configuration.md) using the `log_dir` parameter.
 
 Frameworks that run on Mesos have their output stored to a "work" directory on each machine. By default, this is `MESOS_HOME/work`. Within this directory, a framework's output is placed in files called `stdout` and `stderr` in a directory of the form `slave-X/fw-Y/Z`, where X is the slave ID, Y is the framework ID, and multiple subdirectories Z are created for each attempt to run an executor for the framework. These files can also be accessed via the web UI of the slave daemon.
\ No newline at end of file