Update Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Dragon
[git/dscho.git] / index.html
blob7929e987b11488e0f4ee1decdb3c670652031366
1 <html>
2 <head>
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=17e6b67d689c623802d4bec3511270a89f2a4091;f=blog.css">
7 </head>
8 <body>
9 <div class=content>
10 <h1>Dscho's blog</h1>
11 <div style="position:absolute;top:50px;left:810px;width=400px">
12 <table width=400px bgcolor=#e0e0e0 border=1><tr><td>
13 <p><ol>
14 <li><a href=#1232604722>22 Jan 2009 Let there be images!</a>
15 <li><a href=#1232599693>22 Jan 2009 My blog has style</a>
16 <li><a href=#1232589695>22 Jan 2009 My new blog system... bloGit</a>
17 </td></tr></table>
18 </ol></p>
19 </div>
20 <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Dragon</h6>
21 <a name=1232604722>
22 <h2>Let there be images!</h2>
24 <p>
25 </p><p>
26 One of the most important features of blogs is the ability to insert images.
27 So what would this blog be, if it could not present something that says
28 more than a thousand words?
29 </p><p>
30 So here it goes, my first picture in this blog, taken from my Google Tech
31 Talk in Mountain View:
32 </p><p>
33 <center><img src=dscho.git?a=blob_plain;hb=17e6b67d689c623802d4bec3511270a89f2a4091;f=all-your-rebase.png></center>
34 </p><p>
35 Now this blog starts to look like a real blog...
36 </p>
37 <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Rabbit</h6>
38 <a name=1232599693>
39 <h2>My blog has style</h2>
41 <p>
42 </p><p>
43 It is official. The blog has a style sheet now.
44 </p><p>
45 The major problem was how to design the system such that it would work
46 both locally and on <a href=http://repo.or.cz>repo.or.cz</a> via gitweb.
47 </p><p>
48 Basically, I realized that I'd need a dry run mode anyway, to prevent
49 all my failed attemp.. oops, I meant, to prevent an accidental push
50 when I am at an, ahem, intermediate state of the 'blog' branch.
51 </p><p>
52 Therefore, I could write a different file locally, which I can load
53 into my venerable Firefox.
54 </p><p>
55 The next plans with my new toy are to enable an easy way to support
56 showing images, and then maybe a table of contents. External links
57 would be cool (<a href=http://repo.or.cz>repo.or.cz</a> does not count, it is special-cased), too.
58 </p><p>
59 And later maybe a cut-off, with automatic generation of links to older
60 posts. Hmm, for those, I'll have to change the URL to include the
61 current commit name, so that the images will be found, too...
62 </p><p>
63 Which in turn means that I'll have to parse the source for new
64 images first, so that they can be in the commit that index.html
65 will link to, <u>before</u> it gets committed. Oh well, that cannot be
66 helped! &#x263a;
67 </p>
68 <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Tiger</h6>
69 <a name=1232589695>
70 <h2>My new blog system... bloGit</h2>
72 <p>
73 </p><p>
74 Nowadays, you got to have your blog. Or better: your blogs. Even Junio
75 blogs about Git.
76 </p><p>
77 So I felt a little left behind, having no blog to show off. But then
78 I read about this fantastic new website on the mailing list, called
79 <i>git planet</i> which was supposed to be a place where you could have your
80 Git located blog.
81 </p><p>
82 Except that you could not have your blog <u>there</u>. Instead, it is just an
83 aggregator site.
84 </p><p>
85 I was disappointed.
86 </p><p>
87 But then, I had this (in my humble opinion very cute) idea that I already used to "publish"
88 my slides from the talk "Contributing with Git (AKA All your rebase are
89 belong to us)": back then, I just created a new branch, committed the
90 file, and uploaded the result to <a href=http://repo.or.cz>repo.or.cz</a>, to be downloaded via Gitweb.
91 </p><p>
92 So I asked Pasky via IRC, if he would have any objections if I abused
93 <a href=http://repo.or.cz>repo.or.cz</a> as a blog server. He understood at once, and found it "sounds
94 like a pretty cool idea".
95 </p><p>
96 Of course, just writing plain HTML and committing that is <i>too easy</i>,
97 therefore I decided to write a shell script that would turn some sort
98 of simple text file into proper HTML, commit it, and upload the result.
99 </p><p>
100 Well, about two hours later, I finished the first version of the script
101 turning plain text with minimal markup into an HTML page, and it obviously
102 worked -- otherwise nobody would be able to read this &#x263a;
103 </p>
104 </div>
105 </body>
106 </html>