You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by ij...@apache.org on 2016/05/18 00:46:33 UTC

kafka-site git commit: MINOR: Replace style guide link with scala-lang.org link [Forced Update!]

Repository: kafka-site
Updated Branches:
  refs/heads/asf-site 72f989a51 -> 811faf5f3 (forced update)


MINOR: Replace style guide link with scala-lang.org link

The style guide PDF linked to currently just points to this page anyway.

Closes #13.


Project: http://git-wip-us.apache.org/repos/asf/kafka-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka-site/commit/811faf5f
Tree: http://git-wip-us.apache.org/repos/asf/kafka-site/tree/811faf5f
Diff: http://git-wip-us.apache.org/repos/asf/kafka-site/diff/811faf5f

Branch: refs/heads/asf-site
Commit: 811faf5f35b056d7cc52def5bbdab97eea2bec28
Parents: f53c519
Author: Ryan Coonan <ry...@coonan.me>
Authored: Sat May 14 12:00:37 2016 -0700
Committer: Ismael Juma <is...@juma.me.uk>
Committed: Wed May 18 01:46:21 2016 +0100

----------------------------------------------------------------------
 coding-guide.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka-site/blob/811faf5f/coding-guide.html
----------------------------------------------------------------------
diff --git a/coding-guide.html b/coding-guide.html
index a0b8244..ebc6a46 100644
--- a/coding-guide.html
+++ b/coding-guide.html
@@ -19,7 +19,7 @@ These guidelines are meant to encourage consistency and best practices amongst p
 </ul>
 
 <h2>Scala</h2>
-We are following the style guide given <a href="http://davetron5000.github.com/scala-style/ScalaStyleGuide.pdf ">here</a> (though not perfectly). Below are some specifics worth noting:
+We are following the style guide given <a href="http://docs.scala-lang.org/style/">here</a> (though not perfectly). Below are some specifics worth noting:
 <ul>
 <li>Scala is a very flexible language. Use restraint. Magic cryptic one-liners do not impress us, readability impresses us.</li>
 <li>Use <code>val</code>s when possible.</li>