diary of a window system hacker
can't think of a clever byline

About

Daniel Stone
X ninja
Melbourne, AU

Links

my website
my photos at flickr
x.org
eat.fi

Categories

/ (89)
  tech/ (87)
    collabora/ (2)
    fdo/ (9)
    lca/ (1)
    ubuntu/ (6)
    x/ (43)
      xds/ (3)
  travel/ (2)


Archives

2010-Jul
2010-Jun
2010-Mar
2010-Feb
2009-Dec
2009-Oct
2009-Sep
2009-Aug
2009-Jul
2009-Apr
2009-Mar
2008-Aug
2008-Jul
2008-Jun
2008-May
2008-Feb
2007-Oct
2007-Sep
2007-Jul
2007-Jun
2007-May
2007-Mar
2007-Jan
2006-Nov
2006-Aug
2006-May
2006-Apr
2006-Mar
2006-Feb
2006-Jan
2005-Dec
2005-Nov
2005-Oct
2005-Sep
2005-Aug
2005-Jul
2005-Jun
2005-Apr
2005-Mar
2005-Feb
2005-Jan
2004-Dec
2004-Nov
2004-Oct
2004-Sep
2004-Jun
2004-May
2004-Mar


Calendar

< September 2007 >
SuMoTuWeThFrSa
       1
2 3 4 5 6 7 8
9101112131415
16171819202122
23242526272829
30      

Tue, 18 Sep 2007

git and changelogs

Every time I see a post about changelogs (sorry Behdad, nothing personal), I die a little bit inside.

There are three problems here:
  • In any merge, you always collide horribly on the ChangeLog, and it just makes working with more than one person and/or branch nigh on impossible, so you lose all the benefits of an RCS that actually supports merging.
  • git gives you a system with very lightweight microcommits: in your local tree, you can easily amend, rebase, modify, and walk back, before you push. So, instead of queuing up ten million things such that you need a complicated changelog, do lots of little, relatively self-explanatory commits.
  • Even when you have complicated commits that require explanation (e.g.), just make the commit log sufficiently verbose, so that git blame, gitweb, and any other tool, can offer people the full context, rather than making them dive into an unrelated file and remember the exact date, etc. In X, we just generate ChangeLog from git log, and we're really happy with that so far.
[19:33 | /tech | # | aim - walking home through the park | bed ]