[Groonga-commit] groonga/groonga.org at 8e97c3a [gh-pages] blog en: fix markup

Back to archive index

HAYASHI Kentaro null+****@clear*****
Sun Feb 7 20:46:00 JST 2016


HAYASHI Kentaro	2016-02-07 20:46:00 +0900 (Sun, 07 Feb 2016)

  New Revision: 8e97c3afa617bd5751118dd5544be2d047f3b3b6
  https://github.com/groonga/groonga.org/commit/8e97c3afa617bd5751118dd5544be2d047f3b3b6

  Message:
    blog en: fix markup
    
    Note that http://d3j5vwomefv46c.cloudfront.net/ is now 404.

  Modified files:
    en/_posts/2014-03-29-release.md

  Modified: en/_posts/2014-03-29-release.md (+2 -4)
===================================================================
--- en/_posts/2014-03-29-release.md    2016-02-07 20:40:31 +0900 (04a049f)
+++ en/_posts/2014-03-29-release.md    2016-02-07 20:46:00 +0900 (1897341)
@@ -53,12 +53,10 @@ Here is the summary:
 In fact, ongaeshi who is developer of
 [Milkode](http://milkode.ongaeshi.me/index.html) had tested the impact
 of this feature. Here is the verified graph about increasing the size of
-database. (Thanks to ongaeshi![]()!)
+database. (Thanks to ongaeshi!!!)
 
-<html>
-<img src="http://d3j5vwomefv46c.cloudfront.net/photos/large/843929509.png?1394947803"/>
+[](http://d3j5vwomefv46c.cloudfront.net/photos/large/843929509.png?1394947803)
 
-</html>
 It reveals the fact that if you use previous database as
 is(4.0.0-72-continue), the size of database just increases, but if you
 recreate database, you can suppress the size of one (4.0.0-72-new).
-------------- next part --------------
HTML����������������������������...
Télécharger 



More information about the Groonga-commit mailing list
Back to archive index