Fix the images in the recursive WS design doc
Somehow they were all uploaded as 0 bytes, but that's okay because the URLs
in the design doc were wrong, anyway.
Relavant design doc: https://bazel.build/designs/2016/09/19/recursive-ws-parsing.html, issue #1943.
--
PiperOrigin-RevId: 145799866
MOS_MIGRATED_REVID=145799866
diff --git a/site/assets/ws-diamond.png b/site/assets/ws-diamond.png
index e69de29..154a744 100644
--- a/site/assets/ws-diamond.png
+++ b/site/assets/ws-diamond.png
Binary files differ
diff --git a/site/assets/ws-line.png b/site/assets/ws-line.png
index e69de29..e8bfe7a 100644
--- a/site/assets/ws-line.png
+++ b/site/assets/ws-line.png
Binary files differ
diff --git a/site/assets/ws-multiline.png b/site/assets/ws-multiline.png
index e69de29..f07b43b 100644
--- a/site/assets/ws-multiline.png
+++ b/site/assets/ws-multiline.png
Binary files differ
diff --git a/site/designs/_posts/2016-09-19-recursive-ws-parsing.md b/site/designs/_posts/2016-09-19-recursive-ws-parsing.md
index b161531..f0fcd75 100644
--- a/site/designs/_posts/2016-09-19-recursive-ws-parsing.md
+++ b/site/designs/_posts/2016-09-19-recursive-ws-parsing.md
@@ -39,7 +39,7 @@
Suppose we have a main repository that depends on repo x, and x depends on repo
y:
-<img src="/assets/ws-line.jpg" class="img-responsive">
+<img src="/assets/ws-line.png" class="img-responsive">
In this case, version 1 of "foo" wins. This way, if a library has already
figured out which version works for them, its reverse dependencies do not have
@@ -54,7 +54,7 @@
Report what each chain of dependencies was that wanted the dep and at which
versions:
-<img src="/assets/ws-multiline.jpg" class="img-responsive">
+<img src="/assets/ws-multiline.png" class="img-responsive">
In this case, Bazel would error out with:
@@ -68,7 +68,7 @@
This is also the case with diamond dependencies:
-<img src="/assets/ws-diamond.jpg" class="img-responsive">
+<img src="/assets/ws-diamond.png" class="img-responsive">
This would print:
