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         </head>
   7         <body style="width:800px;background-image:url(dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=paper.jpg);background-repeat:repeat-y;background-attachment:scroll;padding:0px;">
   8                 <div style="width:610px;margin-left:120px;margin-top:50px;align:left;vertical-align:top;">
   9                         <h1>Dscho's blog</h1>
  10                         <div style="position:absolute;top:50px;left:810px;width=400px">
  11                         <table width=400px bgcolor=#e0e0e0 border=1>
  12                         <tr><th>Table of contents:</th></tr>
  13                         <tr><td>
  14                         <p><ul>
  15                         <li><a href=#1232888842>25 Jan 2009 Regular diff with word coloring (as opposed to word diff)</a>
  16                         <li><a href=#1232828715>24 Jan 2009 Ideas for a major revamp of the <i>--preserve-merges</i> handling in <i>git rebase</i></a>
  17                         <li><a href=#1232778113>24 Jan 2009 Thoughts about <i>interactive rebase</i></a>
  18                         <li><a href=#1232745071>23 Jan 2009 Git Logos</a>
  19                         <li><a href=#1232742582>23 Jan 2009 How to deal with files that are not source code when merging</a>
  20                         <li><a href=#1232626236>22 Jan 2009 The UGFWIINI contest</a>
  21                         <li><a href=#1232611542>22 Jan 2009 Top-posting</a>
  22                         <li><a href=#1232607201>22 Jan 2009 Sverre's hat</a>
  23                         <li><a href=#1232604722>22 Jan 2009 Let there be images!</a>
  24                         <li><a href=#1232599693>22 Jan 2009 My blog has style</a>
  25                         </ul></p>
  26                         <a href=dscho.git?a=blob_plain;hb=d6f05382ca9cc377d05499544424e670acdfc7b9;f=index.html>Older posts</a>
  27                         </td></tr></table>
  28                         <br>
  29                         <div style="text-align:right;">
  30                         <a href="dscho.git?a=blob_plain;hb=blog;f=blog.rss"
  31                            title="Subscribe to my RSS feed"
  32                            class="rss" rel="nofollow"
  33                            style="background-color:orange;text-decoration:none;color:white;font-family:sans-serif;">RSS</a>
  34                         </div>
  35                         <br>
  36                         <table width=400px bgcolor=#e0e0e0 border=1>
  37                         <tr><th>About this blog:</th></tr>
  38                         <tr><td>
  39                         <p>It is an active <a href=http://repo.or.cz/w/git/dscho.git?a=blob;f=source-1232626236.txt;h=1edde0467a>abuse</a> of <a href=http://repo.or.cz/>repo.or.cz</a>,
  40                         letting gitweb unpack the objects in the current tip of the branch <i>blog</i>,
  41                         including the images and the RSS feed.
  42                         </p><p>
  43                         Publishing means running a script that collects the posts, turns them into
  44                         HTML, makes sure all the images are checked in, and pushes the result.
  45                         </p><p>
  46                         This blog also serves to grace the world with Dscho's random thoughts on and
  47                         around Git.
  48                         </p>
  49                         </td></tr></table>
  50                         <br>
  51                         <table width=400px bgcolor=#e0e0e0 border=1>
  52                         <tr><th>Links:</th></tr>
  53                         <tr><td>
  54                         <ul>
  55                         <li> <a href=http://git-scm.com/>Git's homepage</a>
  56                         <li> <a href=http://gitster.livejournal.com/>Junio's blog</a>
  57                         <li> <a href=http://www.spearce.org/>Shawn's blog</a> seems to be sitting
  58                               idle ever since he started working for Google...
  59                         <li> <a href=http://torvalds-family.blogspot.com/>Linus' blog</a> does not
  60                               talk much about Git...
  61                         <li> Scott Chacon's <a href=http://whygitisbetterthanx.com/>Why Git is better
  62                              than X</a> site
  63                         <li> <a href=http://vilain.net/>The blog of mugwump</a>
  64                         <li> <a href=http://blogs.gnome.org/newren/>Elijah Newren</a> chose the
  65                               same path as Cogito, offering an alternative porcelain (an approach
  66                               that is doomed in my opinion)
  67                         <li> <a href=http://msysgit.googlecode.com/>The msysGit project</a>, a (mostly)
  68                               failed experiment to lure the many Windows developers out there to
  69                               contribute to Open Source for a change.
  70                         </ul>
  71                         </td></tr></table>
  72                         <br>
  73                         <table width=400px bgcolor=#e0e0e0 border=1>
  74                         <tr><th>Google Ads:</th></tr>
  75                         <tr><td>
  76                         <script type="text/javascript"><!--
  77                         google_ad_client = "pub-5106407705643819";
  78                         /* 300x250, created 1/22/09 */
  79                         google_ad_slot = "6468207338";
  80                         google_ad_width = 300;
  81                         google_ad_height = 250;
  82                         //-->
  83                         </script>
  84                         <script type="text/javascript"
  85                         src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
  86                         </script>
  87                         </td></tr></table>
  88                         </div>
  89                         <h6>Sunday, 25th of January, Anno Domini MMIX, at the hour of the Goat</h6>
  90                         <a name=1232888842>
  91                         <h2>Regular diff with word coloring (as opposed to word diff)</h2>
  92
  93                         <p>
  94                         </p><p>
  95                         You know, if I were a bit faster with everything I do, I could do so much more!
  96                         </p><p>
  97                         For example, Junio's idea that you could keep showing a regular diff, only
  98                         coloring the words that have been removed/deleted.
  99                         </p><p>
 100                         Just imagine looking at the diff of a long line in LaTeX source code.  It
 101                         should be much nicer to the eye to see the complete removed/added sentences
 102                         instead of one sentence with colored words in between, disrupting your read
 103                         flow.
 104                         </p><p>
 105                         Compare these two versions:
 106                         </p><p>
 107                         Regular diff with colored words:
 108                         <blockquote><tt>
 109                         -This sentence has a <font color=red>tyop</font> in it.<br>
 110                         +This sentence has a <font color=green>typo</font> in it.<br>
 111                         </tt></blockquote>
 112                         </p><p>
 113                         Word diff:
 114                         <blockquote><tt>
 115                         This sentence has a <font color=red>tyop</font><font color=green>typo</font> in it.<br>
 116                         </tt></blockquote>
 117                         </p><p>
 118                         And it should not be hard to do at all!
 119                         </p><p>
 120                         In <i>diff&#95;words&#95;show()</i>, we basically get the minus lines as
 121                         <i>diff&#95;words->minus</i> and the plus lines as <i>diff&#95;words->plus</i>.  The
 122                         function then prepares the word lists and calls the xdiff engine to do all the
 123                         hard work, analyzing the result from xdiff and printing the lines in
 124                         <i>fn&#95;out&#95;diff&#95;words&#95;aux()</i>.
 125                         </p><p>
 126                         So all that would have to be changed would be to <u>record</u> the positions
 127                         of the removed/added words instead of outputting them, and at the end printing
 128                         the minus/plus buffers using the recorded information to color the words.
 129                         </p><p>
 130                         This would involve
 131                         </p><p>
 132                         <ul>
 133                         <li>adding two new members holding the offsets in the <i>diff&#95;words</i>
 134                         struct,
 135                         <li>having a special handling for that mode in
 136                         <i>fn&#95;out&#95;diff&#95;words&#95;aux()</i> that appends the offsets and
 137                         returns,
 138                         <li>adding a function <i>show&#95;lines&#95;with&#95;colored&#95;words()</i> that
 139                         outputs a buffer with a given prefix ('-' or '+') and coloring the words at
 140                         given offsets with a given color,
 141                         <li>modify <i>diff&#95;words&#95;show()</i> to call that function for the "special
 142                         case: only removal" and at the end of the function, and
 143                         <li> disabling the <i>fwrite()</i> at the end of <i>diff<u>words</u>show()</i> for that
 144                         mode.
 145                         </ul>
 146                         </p><p>
 147                         Of course, the hardest part is to find a nice user interface for that.  Maybe
 148                         <i>--colored-words</i>? &#x263a;
 149                         </p>
 150                         <h6>Saturday, 24th of January, Anno Domini MMIX, at the hour of the Pig</h6>
 151                         <a name=1232828715>
 152                         <h2>Ideas for a major revamp of the <i>--preserve-merges</i> handling in <i>git rebase</i></h2>
 153
 154                         <p>
 155                         </p><p>
 156                         As probably everybody agrees, the code to preserve merges is a big mess
 157                         right now.
 158                         </p><p>
 159                         Worse, the whole concept of "pick <merge-sha1>" just does not fly well.
 160                         </p><p>
 161                         So I started a <u>major</u> cleanup, which happens to reduce the code very
 162                         nicely so far.
 163                         </p><p>
 164                         It will take a few days to flesh out, I guess, but these are the major
 165                         ideas of my work:
 166                         </p><p>
 167                         <b>pick $sha1</b><br>
 168                         <blockquote>will only work on non-merges in the future.</blockquote>
 169                         <b>merge $sha1 [$sha1...] was $sha1 Merge ...</b><br>
 170                         <blockquote>will merge the given list of commits into the current HEAD, for
 171                                 the user's reference and to keep up-to-date what was rewritten,
 172                                 the original merge is shown after the keyword "was" (which is not
 173                                 a valid SHA-1, luckily).</blockquote>
 174                         <b>goto $sha1</b><br>
 175                         <blockquote>will reset the HEAD to the given commit.</blockquote>
 176                         <b>$sha1'</b><br>
 177                         <blockquote>for merge and goto, if a $sha1 ends in a single quote, the
 178                                 rewritten commit is substituted (if there is one).</blockquote>
 179                         </p><p>
 180                         Example:
 181                         </p><p>
 182 <pre>
 183 A - B - - - E
 184   \       /
 185     C - D
 186 </pre>
 187                         </p><p>
 188                         could yield this TODO script:
 189                         </p><p>
 190 <pre>
 191         pick A
 192         pick C
 193         pick D
 194         goto A'
 195         pick B
 196         merge D' was E
 197 </pre>
 198                         </p><p>
 199                         This should lead to a much more intuitive user experience.
 200                         </p><p>
 201                         I am very sorry if somebody actually scripted <i>rebase -i -p</i> (by setting
 202                         GIT_EDITOR with a script), but I am very certain that this cleanup is
 203                         absolutely necessary to make <i>rebase -i -p</i> useful.
 204                         </p>
 205                         <h6>Saturday, 24th of January, Anno Domini MMIX, at the hour of the Dragon</h6>
 206                         <a name=1232778113>
 207                         <h2>Thoughts about <i>interactive rebase</i></h2>
 208
 209                         <p>
 210                         </p><p>
 211                         Somebody mentioned that my <i>my-next</i> branch is a mess, as it mixes all
 212                         kinds of topics.
 213                         </p><p>
 214                         That is undeniably true, however, there is a good reason that I do not
 215                         have a lot of topic branches: I work on more than just one computer.
 216                         </p><p>
 217                         To make sure that I do not lose a commit by mistake, I always <i>rebase -i</i>
 218                         the <i>my-next</i> branch of the computer I happen to work on on top of the
 219                         <i>my-next</i> branch I fetch from <a href=http://repo.or.cz>repo.or.cz</a>.
 220                         </p><p>
 221                         To rebase a lot of topic branches at the same time seems a bit complicated.
 222                         But that is actually what the <i>-p</i> option (preserve merges) is all about.
 223                         </p><p>
 224                         The only problem is that the code for <i>rebase -i -p</i> has been messed up
 225                         recently, quite successfully, I might add.
 226                         </p><p>
 227                         Worse, some people are pushing for a completely and total unintuitive syntax.
 228                         </p><p>
 229                         So maybe I will start to work on <i>-p</i> again, for my own use (I should learn
 230                         to heed the principle more: work on things I can use myself).
 231                         </p><p>
 232                         My current idea is to implement a "goto" statement that will jump to another
 233                         commit.  To make it easily usable, I will add the semantics that "goto" will
 234                         always try to go to the <u>rewritten</u> version of the given commit; if the user
 235                         wanted to have the original commit, she has to paste the unabbreviated commit
 236                         name.
 237                         </p><p>
 238                         The more I think about it, the more I actually like this idea &#x263a;
 239                         </p><p>
 240                         Of course, working on this little project means that I will have to cope with
 241                         that ugly code again.  *urgh*
 242                         </p>
 243                         <h6>Friday, 23rd of January, Anno Domini MMIX, at the hour of the Pig</h6>
 244                         <a name=1232745071>
 245                         <h2>Git Logos</h2>
 246
 247                         <p>
 248                         </p><p>
 249                         The other day, when I did not exactly have too much time on my hands, but
 250                         definitely too much motivation, I played around creating several logos.
 251                         </p><p>
 252                         An ambigram (if you turn it 180 degrees around the appropriate axis, it looks
 253                         exactly the same as unrotated):
 254                         </p><p>
 255                         <center>
 256                                 <table border=0>
 257                                         <tr>
 258                                                 <td align=center>
 259                                                         <embed type="image/svg+xml"
 260                                                                 src="dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=git-ambigram.svg" width=317 />
 261                                                 </td>
 262                                         </tr>
 263                                         <tr>
 264                                                 <td align=center>
 265                                                         <a href=dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=git-ambigram.svg>git-ambigram.svg</a>
 266                                                 </td>
 267                                         </tr>
 268                                 </table>
 269                         </center>
 270                         </p><p>
 271                         A play on gitk:
 272                         </p><p>
 273                         <center>
 274                                 <table border=0>
 275                                         <tr>
 276                                                 <td align=center>
 277                                                         <embed type="image/svg+xml"
 278                                                                 src="dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=git-gitk-logo.svg" width=325 />
 279                                                 </td>
 280                                         </tr>
 281                                         <tr>
 282                                                 <td align=center>
 283                                                         <a href=dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=git-gitk-logo.svg>git-gitk-logo.svg</a>
 284                                                 </td>
 285                                         </tr>
 286                                 </table>
 287                         </center>
 288                         </p><p>
 289                         A play on the test you have to go through before getting new glasses:
 290                         </p><p>
 291                         <center>
 292                                 <table border=0>
 293                                         <tr>
 294                                                 <td align=center>
 295                                                         <embed type="image/svg+xml"
 296                                                                 src="dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=git-visual-test.svg" width=325 />
 297                                                 </td>
 298                                         </tr>
 299                                         <tr>
 300                                                 <td align=center>
 301                                                         <a href=dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=git-visual-test.svg>git-visual-test.svg</a>
 302                                                 </td>
 303                                         </tr>
 304                                 </table>
 305                         </center>
 306                         </p><p>
 307                         This is Henrik Nyh's logo (converted to .svg by yours truly):
 308                         </p><p>
 309                         <center>
 310                                 <table border=0>
 311                                         <tr>
 312                                                 <td align=center>
 313                                                         <embed type="image/svg+xml"
 314                                                                 src="dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=gitlogo.svg" width=165 />
 315                                                 </td>
 316                                         </tr>
 317                                         <tr>
 318                                                 <td align=center>
 319                                                         <a href=dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=gitlogo.svg>gitlogo.svg</a>
 320                                                 </td>
 321                                         </tr>
 322                                 </table>
 323                         </center>
 324                         </p><p>
 325                         And of course, the original logo...
 326                         </p><p>
 327                         <center>
 328                                 <table border=0>
 329                                         <tr>
 330                                                 <td align=center>
 331                                                         <embed type="image/svg+xml"
 332                                                                 src="dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=original-git-logo.svg" width=165 />
 333                                                 </td>
 334                                         </tr>
 335                                         <tr>
 336                                                 <td align=center>
 337                                                         <a href=dscho.git?a=blob_plain;hb=aaa9edafbe6ca5349ad7b36848fb294e5f4fc529;f=original-git-logo.svg>original-git-logo.svg</a>
 338                                                 </td>
 339                                         </tr>
 340                                 </table>
 341                         </center>
 342                         </p><p>
 343                         Maybe some of you have fun with them...
 344                         </p>
 345                         <h6>Friday, 23rd of January, Anno Domini MMIX, at the hour of the Pig</h6>
 346                         <a name=1232742582>
 347                         <h2>How to deal with files that are not source code when merging</h2>
 348
 349                         <p>
 350                         </p><p>
 351                         Last week, one of the mentors of last year's <a href=http://code.google.com/soc>
 352                         Summer of Code</a> mentioned the idea that merge strategies are in dear need
 353                         for file types other than source code.
 354                         </p><p>
 355                         I think this idea is awesome, even if I cannot bring myself to believe that
 356                         any of the file types would make a good Summer of Code project: either they
 357                         are too complicated (think raster images such as .png or even .jpg), or they
 358                         are too straight-forward (think LaTeX, where all that is needed is a good
 359                         graphical user interface to inspect the three versions: <i>ours</i>, <i>baseline</i>
 360                         and <i>theirs</i>).
 361                         </p><p>
 362                         The LaTeX idea would be a good project for me to mentor, though: I have a
 363                         pretty clear idea how it should be done; I just lack the time (and motivation)
 364                         to do it myself.
 365                         </p><p>
 366                         As for OpenOffice text documents, vector graphics (such as .svg), or more
 367                         specific data such as spreadsheets, I think that all of these are really
 368                         difficult: the problem is not so much the implementation (i.e. the programming
 369                         part of it), but the design.
 370                         </p><p>
 371                         This design should involve much more than a Summer of Code project is about:
 372                         you would need to survey users' expectations, and at least the mentor -- if
 373                         not the student -- would need to be an expert in usability questions, which
 374                         is rather unlikely in the realm of Open Source.
 375                         </p><p>
 376                         Maybe this is the missing part in Open Source: we have many brilliant
 377                         programmers, but next to nobody with a good idea how to design intuitive
 378                         user interfaces.
 379                         </p><p>
 380                         That might be related to the fact that brilliant software engineers, as they
 381                         can be found in Open Source, are not exactly known for their social skills,
 382                         a human trait that seems to be a very important prerequisite for designing
 383                         intuitive user interfaces.
 384                         </p><p>
 385                         Well, I have <a href=http://git.or.cz/gitwiki/SoC2009Ideas#head-6188833471f79f277e162ef9fbe1592aa10b5f6c>
 386                         added</a> the proposal to Git's Summer of Code idea page on the Git Wiki; We will
 387                         see what comes out of it.
 388                         </p>
 389                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Goat</h6>
 390                         <a name=1232626236>
 391                         <h2>The UGFWIINI contest</h2>
 392
 393                         <p>
 394                         </p><p>
 395                         Just in case somebody finds this blog, here is a challenge.  Inspired by my
 396                         own little hack (this blog), I announce the "Using Git For What It Is Not
 397                         Intended" contest.
 398                         </p><p>
 399                         And it is especially cool, since the acronym sounds cool!  You might miss
 400                         this fact if you do no know that I pronounce the "F" like an "A" so that
 401                         it sounds cool.
 402                         </p><p>
 403                         This will be a running contest; whenever I have 10 valid applications, I
 404                         will announce a winner on the Git mailing list.
 405                         </p><p>
 406                         So, what accounts for a valid application?
 407                         </p><p>
 408                         <ul>
 409                         <li> You must use a Git program (the term is used loosely here, GitWeb is
 410                              considered a Git program, for example).
 411                         <li> The program must be intended for something completely different than
 412                              what you are using it for.  E.g. GitWeb -- which was intended to let
 413                              you browse through the history using your web browser -- is used
 414                              to serve a blog to the wide world.
 415                         <li> You must be able to prove that you actually used the Git program to
 416                              the purpose you claim, preferably in a live demonstration like this
 417                              one.
 418                         <li> Nobody and nothing must be harmed in the process (except your
 419                              laughing muscle, that's okay).
 420                         </ul>
 421                         </p><p>
 422                         So, how does such an abuse look like?
 423                         </p><p>
 424                         <ul>
 425                         <li> ... like this blog.
 426                         <li> Managing your mail (in maildir format) in a Git repository.
 427                         <li> Finding duplicate files by
 428                         <table
 429                                                         border=1 bgcolor=black>
 430                                                 <tr><td bgcolor=lightblue colspan=3>
 431                                                         &nbsp;
 432                                                 </td></tr>
 433                                                 <tr><td>
 434                                                         <table cellspacing=5 border=0
 435                                                                  style="color:white;">
 436                                                         <tr><td>
 437                                         <pre>
 438 $ git init
 439 $ git add .
 440 $ git ls-files --stage | sort -k2 | uniq -d -s7 -w40
 441                 </pre>
 442                                                         </td></tr>
 443                                                         </table>
 444                                                 </td></tr>
 445                                                 </table>
 446                         <li> Abusing the Git alias mechanism to call scripts defined directly in
 447                              the config.
 448                         </ul>
 449                         </p><p>
 450                         I am really looking forward to all of your submissions... *chuckles*
 451                         </p><p>
 452                         </p>
 453                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Snake</h6>
 454                         <a name=1232611542>
 455                         <h2>Top-posting</h2>
 456
 457                         <p>
 458                         </p><p>
 459                         Okay, last post for a while.  But this is something that is nagging me
 460                         tremendously.  I should probably just let go, but in my deepest inner self,
 461                         really close to my heart, I refuse to believe that any human beings could
 462                         be incapable of certain degrees of reason.
 463                         </p><p>
 464                         Take the example of top-posting.  Everybody who read a top-posted email
 465                         knows that you have to scroll down, possibly weeding through tons of
 466                         pages to find out what the heck the author of the last reply was replying
 467                         to.
 468                         </p><p>
 469                         Never mind that it would take the author of the reply just a couple of
 470                         seconds to remove all the irrelevant stuff -- as she already knows what
 471                         is the relevant part, saving minutes, in case of mailing lists hours,
 472                         easily, to the readers who otherwise would have to discern what is
 473                         irrelevant and what is relevant first.
 474                         </p><p>
 475                         It is a horrible time waste.  But of course not for the top-poster.
 476                         </p><p>
 477                         The problem is that I frequently run into such people, and when I write
 478                         them a polite mail, explaining to them that it is impolite to top-post,
 479                         and why, the answers I get sometimes make me check if the sky is still up
 480                         and the earth down.  Yesterday was an example of such a dubitable
 481                         pleasure.
 482                         </p><p>
 483                         Most funny are the ridiculous attempts by those persons at explaining why
 484                         top-posting is <i>so</i> much superior to anything else.
 485                         </p><p>
 486                         Which is good, because if they were not that funny, they would be pretty sad.
 487                         </p>
 488                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Dragon</h6>
 489                         <a name=1232607201>
 490                         <h2>Sverre's hat</h2>
 491
 492                         <p>
 493                         </p><p>
 494                         The fun part about a blog is that you can talk about less technical stuff.
 495                         For example, Sverre's hat.
 496                         </p><p>
 497                         Let me start a bit earlier, so that you get the context.
 498                         </p><p>
 499                         Last year, at the <a href=http://git.or.cz/gitwiki/GitTogether>GitTogether</a>,
 500                         we had an <a href=http://en.wikipedia.org/wiki/Unconference>unconference style
 501                         conference</a>, which basically meant that it was our job to decide what
 502                         we want to talk about.
 503                         </p><p>
 504                         It turned out to be pretty hard, because there was so much we wanted to
 505                         discuss, and because we wanted to get to know each other, and we wanted to
 506                         do some hacking.
 507                         </p><p>
 508                         So to help us decide what subjects, and in which order we wanted to have
 509                         scheduled, Shawn opened a series on <a href=http://moderator.appspot.com/>
 510                         Google Moderator</a>, a nifty, yet simple application which allows a group
 511                         to agree quickly on an agenda.
 512                         </p><p>
 513                         It worked quite well; However, that little saboteur displayed his sense of
 514                         humor so overtly that some entertaining Gitter put the question "Should Sverre
 515                         wear a hat?" on the agenda.
 516                         </p><p>
 517                         Sure enough, the subject got voted up, and eventually, we got Sverre a hat:
 518                         </p><p>
 519                         <center><img src=dscho.git?a=blob_plain;hb=30319f7436828cd15db8a531a0057351d8e361c0;f=sverre-hat.jpg sverre-hat.jpg></center>
 520                         </p><p>
 521                         By the way, another thing I like about this blog engine is that there are no
 522                         comments...  Nothing is more annoying than leaving a comment on a blog,
 523                         forgetting about it for a few months, and then finding somebody answered
 524                         ages ago.
 525                         </p><p>
 526                         Update: Sverre says it was dsymonds idea.
 527                         </p>
 528                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Dragon</h6>
 529                         <a name=1232604722>
 530                         <h2>Let there be images!</h2>
 531
 532                         <p>
 533                         </p><p>
 534                         One of the most important features of blogs is the ability to insert images.
 535                         So what would this blog be, if it could not present something that says
 536                         more than a thousand words?
 537                         </p><p>
 538                         So here it goes, my first picture in this blog, taken from my Google Tech
 539                         Talk in Mountain View:
 540                         </p><p>
 541                         <center><img src=dscho.git?a=blob_plain;hb=85b89d1cd73acd65ca4381be901d50287dde8170;f=all-your-rebase.png width=500px></center>
 542                         </p><p>
 543                         Now this blog starts to look like a real blog...
 544                         </p>
 545                         <h6>Thursday, 22nd of January, Anno Domini MMIX, at the hour of the Rabbit</h6>
 546                         <a name=1232599693>
 547                         <h2>My blog has style</h2>
 548
 549                         <p>
 550                         </p><p>
 551                         It is official.  The blog has a style sheet now.
 552                         </p><p>
 553                         The major problem was how to design the system such that it would work
 554                         both locally and on <a href=http://repo.or.cz>repo.or.cz</a> via gitweb.
 555                         </p><p>
 556                         Basically, I realized that I'd need a dry run mode anyway, to prevent
 557                         all my failed attemp.. oops, I meant, to prevent an accidental push
 558                         when I am at an, ahem, intermediate state of the 'blog' branch.
 559                         </p><p>
 560                         Therefore, I could write a different file locally, which I can load
 561                         into my venerable Firefox.
 562                         </p><p>
 563                         The next plans with my new toy are to enable an easy way to support
 564                         showing images, and then maybe a table of contents.  External links
 565                         would be cool (<a href=http://repo.or.cz>repo.or.cz</a> does not count, it is special-cased), too.
 566                         </p><p>
 567                         And later maybe a cut-off, with automatic generation of links to older
 568                         posts.  Hmm, for those, I'll have to change the URL to include the
 569                         current commit name, so that the images will be found, too...
 570                         </p><p>
 571                         Which in turn means that I'll have to parse the source for new
 572                         images first, so that they can be in the commit that index.html
 573                         will link to, <u>before</u> it gets committed.  Oh well, that cannot be
 574                         helped! &#x263a;
 575                         </p>
 576                 </div>
 577         </body>
 578 </html>