Make https:// compatible

[personal/website.git] / source / blog / posts / 2009 / 08 / allocations-graphs.rst

diff --git a/source/blog/posts/2009/08/allocations-graphs.rst b/source/blog/posts/2009/08/allocations-graphs.rst
index 05ca3a53014b2dd294dcd27b215d875ff5a42308..00190c92d3adfa3f30654a679a907ea4feb35c31 100644 (file)
--- a/source/blog/posts/2009/08/allocations-graphs.rst
+++ b/source/blog/posts/2009/08/allocations-graphs.rst
@@ -9,8 +9,8 @@ Again, all graphs (as the graph title says), are taken using the `Naive GC`__
 (stats code still not public yet :) and you can find the code for it in my `D
 GC benchmark`__ repository.
 
 (stats code still not public yet :) and you can find the code for it in my `D
 GC benchmark`__ repository.
 

-__ http://git.llucax.com.ar/w/software/dgc/naive.git
-__ http://git.llucax.com.ar/w/software/dgc/dgcbench.git
+__ https://git.llucax.com.ar/w/software/dgc/naive.git
+__ https://git.llucax.com.ar/w/software/dgc/dgcbench.git

 
 This time the (big) graphs are in EPS format because I could render them in PNG
 as big as I wanted and I didn't had the time to fix that =S
 
 This time the (big) graphs are in EPS format because I could render them in PNG
 as big as I wanted and I didn't had the time to fix that =S


@@ -48,7 +48,7 @@ histogram of cell sizes. The histogram differentiates cells with and without
 the ``NO_SCAN`` bit, which might be useful in terms on seeing how bad the
 effect of false positives could be.
 
 the ``NO_SCAN`` bit, which might be useful in terms on seeing how bad the
 effect of false positives could be.
 

-__ http://git.llucax.com.ar/w/software/dgc/naive.git
+__ https://git.llucax.com.ar/w/software/dgc/naive.git

 
 You can easily see how allocation time peeks match allocations that triggered
 a collection for example, and how bad can it be the effect of false positives,
 
 You can easily see how allocation time peeks match allocations that triggered
 a collection for example, and how bad can it be the effect of false positives,