index.html

   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=832be85c785c80202f17b87db7f063ae57ec2cac;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=#1232611542>22 Jan 2009 Top-posting</a>
  15 <li><a href=#1232607201>22 Jan 2009 Sverre's hat</a>
  16 <li><a href=#1232604722>22 Jan 2009 Let there be images!</a>
  17 <li><a href=#1232599693>22 Jan 2009 My blog has style</a>
  18 <li><a href=#1232589695>22 Jan 2009 My new blog system... bloGit</a>
  19 </td></tr></table>
  20 </ol></p>
  21 </div>
  22                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Snake</h6>
  23                         <a name=1232611542>
  24                         <h2>Top-posting</h2>
  25
  26                         <p>
  27                         </p><p>
  28                         Okay, last post for a while.  But this is something that is nagging me
  29                         tremendously.  I should probably just let go, but in my deepest inner self,
  30                         really close to my heart, I refuse to believe that any human beings could
  31                         be incapable of certain degrees of reason.
  32                         </p><p>
  33                         Take the example of top-posting.  Everybody who read a top-posted email
  34                         knows that you have to scroll down, possibly weeding through tons of
  35                         pages to find out what the heck the author of the last reply was replying
  36                         to.
  37                         </p><p>
  38                         Never mind that it would take the author of the reply just a couple of
  39                         seconds to remove all the irrelevant stuff -- as she already knows what
  40                         is the relevant part, saving minutes, in case of mailing lists hours,
  41                         easily, to the readers who otherwise would have to discern what is
  42                         irrelevant and what is relevant first.
  43                         </p><p>
  44                         It is a horrible time waste.  But of course not for the top-poster.
  45                         </p><p>
  46                         The problem is that I frequently run into such people, and when I write
  47                         them a polite mail, explaining to them that it is impolite to top-post,
  48                         and why, the answers I get sometimes make me check if the sky is still up
  49                         and the earth down.  Yesterday was an example of such a dubitable
  50                         pleasure.
  51                         </p><p>
  52                         Most funny are the ridiculous attempts by those persons at explaining why
  53                         top-posting is <i>so</i> much superior to anything else.
  54                         </p><p>
  55                         Which is good, because if they were not that funny, they would be pretty sad.
  56                         </p>
  57                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Dragon</h6>
  58                         <a name=1232607201>
  59                         <h2>Sverre's hat</h2>
  60
  61                         <p>
  62                         </p><p>
  63                         The fun part about a blog is that you can talk about less technical stuff.
  64                         For example, Sverre's hat.
  65                         </p><p>
  66                         Let me start a bit earlier, so that you get the context.
  67                         </p><p>
  68                         Last year, at the <a href=http://git.or.cz/gitwiki/GitTogether>GitTogether</a>,
  69                         we had an <a href=http://en.wikipedia.org/wiki/Unconference>unconference style
  70                         conference</a>, which basically meant that it was our job to decide what
  71                         we want to talk about.
  72                         </p><p>
  73                         It turned out to be pretty hard, because there was so much we wanted to
  74                         discuss, and because we wanted to get to know each other, and we wanted to
  75                         do some hacking.
  76                         </p><p>
  77                         So to help us decide what subjects, and in which order we wanted to have
  78                         scheduled, Shawn opened a series on <a href=http://moderator.appspot.com/>
  79                         Google Moderator</a>, a nifty, yet simple application which allows a group
  80                         to agree quickly on an agenda.
  81                         </p><p>
  82                         It worked quite well; However, that little saboteur displayed his sense of
  83                         humor so overtly that some entertaining Gitter put the question "Should Sverre
  84                         wear a hat?" on the agenda.
  85                         </p><p>
  86                         Sure enough, the subject got voted up, and eventually, we got Sverre a hat:
  87                         </p><p>
  88                         <center><img src=dscho.git?a=blob_plain;hb=832be85c785c80202f17b87db7f063ae57ec2cac;f=sverre-hat.jpg></center>
  89                         </p><p>
  90                         By the way, another thing I like about this blog engine is that there are no
  91                         comments...  Nothing is more annoying than leaving a comment on a blog,
  92                         forgetting about it for a few months, and then finding somebody answered
  93                         ages ago.
  94                         </p>
  95                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Dragon</h6>
  96                         <a name=1232604722>
  97                         <h2>Let there be images!</h2>
  98
  99                         <p>
 100                         </p><p>
 101                         One of the most important features of blogs is the ability to insert images.
 102                         So what would this blog be, if it could not present something that says
 103                         more than a thousand words?
 104                         </p><p>
 105                         So here it goes, my first picture in this blog, taken from my Google Tech
 106                         Talk in Mountain View:
 107                         </p><p>
 108                         <center><img src=dscho.git?a=blob_plain;hb=832be85c785c80202f17b87db7f063ae57ec2cac;f=all-your-rebase.png></center>
 109                         </p><p>
 110                         Now this blog starts to look like a real blog...
 111                         </p>
 112                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Rabbit</h6>
 113                         <a name=1232599693>
 114                         <h2>My blog has style</h2>
 115
 116                         <p>
 117                         </p><p>
 118                         It is official.  The blog has a style sheet now.
 119                         </p><p>
 120                         The major problem was how to design the system such that it would work
 121                         both locally and on <a href=http://repo.or.cz>repo.or.cz</a> via gitweb.
 122                         </p><p>
 123                         Basically, I realized that I'd need a dry run mode anyway, to prevent
 124                         all my failed attemp.. oops, I meant, to prevent an accidental push
 125                         when I am at an, ahem, intermediate state of the 'blog' branch.
 126                         </p><p>
 127                         Therefore, I could write a different file locally, which I can load
 128                         into my venerable Firefox.
 129                         </p><p>
 130                         The next plans with my new toy are to enable an easy way to support
 131                         showing images, and then maybe a table of contents.  External links
 132                         would be cool (<a href=http://repo.or.cz>repo.or.cz</a> does not count, it is special-cased), too.
 133                         </p><p>
 134                         And later maybe a cut-off, with automatic generation of links to older
 135                         posts.  Hmm, for those, I'll have to change the URL to include the
 136                         current commit name, so that the images will be found, too...
 137                         </p><p>
 138                         Which in turn means that I'll have to parse the source for new
 139                         images first, so that they can be in the commit that index.html
 140                         will link to, <u>before</u> it gets committed.  Oh well, that cannot be
 141                         helped! &#x263a;
 142                         </p>
 143                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Tiger</h6>
 144                         <a name=1232589695>
 145                         <h2>My new blog system... bloGit</h2>
 146
 147                         <p>
 148                         </p><p>
 149                         Nowadays, you got to have your blog.  Or better: your blogs.  Even Junio
 150                         blogs about Git.
 151                         </p><p>
 152                         So I felt a little left behind, having no blog to show off.  But then
 153                         I read about this fantastic new website on the mailing list, called
 154                         <i>git planet</i> which was supposed to be a place where you could have your
 155                         Git located blog.
 156                         </p><p>
 157                         Except that you could not have your blog <u>there</u>.  Instead, it is just an
 158                         aggregator site.
 159                         </p><p>
 160                         I was disappointed.
 161                         </p><p>
 162                         But then, I had this (in my humble opinion very cute) idea that I already used to "publish"
 163                         my slides from the talk "Contributing with Git (AKA All your rebase are
 164                         belong to us)": back then, I just created a new branch, committed the
 165                         file, and uploaded the result to <a href=http://repo.or.cz>repo.or.cz</a>, to be downloaded via Gitweb.
 166                         </p><p>
 167                         So I asked Pasky via IRC, if he would have any objections if I abused
 168                         <a href=http://repo.or.cz>repo.or.cz</a> as a blog server.  He understood at once, and found it "sounds
 169                         like a pretty cool idea".
 170                         </p><p>
 171                         Of course, just writing plain HTML and committing that is <i>too easy</i>,
 172                         therefore I decided to write a shell script that would turn some sort
 173                         of simple text file into proper HTML, commit it, and upload the result.
 174                         </p><p>
 175                         Well, about two hours later, I finished the first version of the script
 176                         turning plain text with minimal markup into an HTML page, and it obviously
 177                         worked -- otherwise nobody would be able to read this &#x263a;
 178                         </p>
 179                 </div>
 180         </body>
 181 </html>