Let there be images!
[git/dscho.git] / index.html
blob57d40173d1ae67e84ace58effd631cb4be4a66a5
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=blog;f=blog.css">
7 </head>
8 <body>
9 <div class=content>
10 <h1>Dscho's blog</h1>
11 <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Rabbit</h6>
12 <h2>My blog has style</h2>
14 <p>
15 </p><p>
16 It is official. The blog has a style sheet now.
17 </p><p>
18 The major problem was how to design the system such that it would work
19 both locally and on <a href=http://repo.or.cz>repo.or.cz</a> via gitweb.
20 </p><p>
21 Basically, I realized that I'd need a dry run mode anyway, to prevent
22 all my failed attemp.. oops, I meant, to prevent an accidental push
23 when I am at an, ahem, intermediate state of the 'blog' branch.
24 </p><p>
25 Therefore, I could write a different file locally, which I can load
26 into my venerable Firefox.
27 </p><p>
28 The next plans with my new toy are to enable an easy way to support
29 showing images, and then maybe a table of contents. External links
30 would be cool (<a href=http://repo.or.cz>repo.or.cz</a> does not count, it is special-cased), too.
31 </p><p>
32 And later maybe a cut-off, with automatic generation of links to older
33 posts. Hmm, for those, I'll have to change the URL to include the
34 current commit name, so that the images will be found, too...
35 </p><p>
36 Which in turn means that I'll have to parse the source for new
37 images first, so that they can be in the commit that index.html
38 will link to, <u>before</u> it gets committed. Oh well, that cannot be
39 helped! &#x263a;
40 </p>
41 <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Tiger</h6>
42 <h2>My new blog system... bloGit</h2>
44 <p>
45 </p><p>
46 Nowadays, you got to have your blog. Or better: your blogs. Even Junio
47 blogs about Git.
48 </p><p>
49 So I felt a little left behind, having no blog to show off. But then
50 I read about this fantastic new website on the mailing list, called
51 <i>git planet</i> which was supposed to be a place where you could have your
52 Git located blog.
53 </p><p>
54 Except that you could not have your blog <u>there</u>. Instead, it is just an
55 aggregator site.
56 </p><p>
57 I was disappointed.
58 </p><p>
59 But then, I had this (in my humble opinion very cute) idea that I already used to "publish"
60 my slides from the talk "Contributing with Git (AKA All your rebase are
61 belong to us)": back then, I just created a new branch, committed the
62 file, and uploaded the result to <a href=http://repo.or.cz>repo.or.cz</a>, to be downloaded via Gitweb.
63 </p><p>
64 So I asked Pasky via IRC, if he would have any objections if I abused
65 <a href=http://repo.or.cz>repo.or.cz</a> as a blog server. He understood at once, and found it "sounds
66 like a pretty cool idea".
67 </p><p>
68 Of course, just writing plain HTML and committing that is <i>too easy</i>,
69 therefore I decided to write a shell script that would turn some sort
70 of simple text file into proper HTML, commit it, and upload the result.
71 </p><p>
72 Well, about two hours later, I finished the first version of the script
73 turning plain text with minimal markup into an HTML page, and it obviously
74 worked -- otherwise nobody would be able to read this &#x263a;
75 </p>
76 </div>
77 </body>
78 </html>