3 <title>Dscho's blog
</title>
4 <meta http-equiv=
"Content-Type"
5 content=
"text/html; charset=UTF-8"/>
6 <link rel=
"stylesheet" type=
"text/css" href=
"dscho.git?a=blob_plain;hb=blog;f=blog.css">
11 <h6>Thursday,
22nd of January, Anno Domini MMIX, at the hour of the Tiger
</h6>
12 <h2>My new blog system... bloGit
</h2>
16 Nowadays, you got to have your blog. Or better: your blogs. Even Junio
19 So I felt a little left behind, having no blog to show off. But then
20 I read about this fantastic new website on the mailing list, called
21 <i>git planet
</i> which was supposed to be a place where you could have your
24 Except that you could not have your blog
<u>there
</u>. Instead, it is just an
29 But then, I had this (in my humble opinion very cute) idea that I already used to
"publish"
30 my slides from the talk
"Contributing with Git (AKA All your rebase are
31 belong to us)": back then, I just created a new branch, committed the
32 file, and uploaded the result to
<a href=http://repo.or.cz
>repo.or.cz
</a>, to be downloaded via Gitweb.
34 So I asked Pasky via IRC, if he would have any objections if I abused
35 <a href=http://repo.or.cz
>repo.or.cz
</a> as a blog server. He understood at once, and found it
"sounds
36 like a pretty cool idea".
38 Of course, just writing plain HTML and committing that is
<i>too easy
</i>,
39 therefore I decided to write a shell script that would turn some sort
40 of simple text file into proper HTML, commit it, and upload the result.
42 Well, about two hours later, I finished the first version of the script
43 turning plain text with minimal markup into an HTML page, and it obviously
44 worked -- otherwise nobody would be able to read this
☺