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