kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ij...@apache.org
Subject kafka-site git commit: MINOR: Replace style guide link with scala-lang.org link
Date Wed, 18 May 2016 00:45:32 GMT
Repository: kafka-site
Updated Branches:
  refs/heads/asf-site f53c5192f -> 72f989a51


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

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

Closes #1393.


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

Branch: refs/heads/asf-site
Commit: 72f989a5139e3f78fc2bdee9cc3b32f48808b4fd
Parents: f53c519
Author: Ryan Coonan <ryan@coonan.me>
Authored: Sat May 14 12:00:37 2016 -0700
Committer: Ismael Juma <ismael@juma.me.uk>
Committed: Wed May 18 01:45:06 2016 +0100

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


http://git-wip-us.apache.org/repos/asf/kafka-site/blob/72f989a5/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>


Mime
View raw message