úÎ&ù%ú     ;Call out to the shell, and collect the result as a String.  The command Options to the command Result DAsk Git for changes in general; we accept an options argument which H will be passed onto Git, so you can customize by using any of the many  options to  which Git understands.  Tricky bits: we can' t pass Git "", because it won't treat it as non-existent, . so the implementation needs to reflect this. 7Nothing fancy: just get the entire repository history. AAsk Git for all changes, since the last tag. Conscientious folks 4 tag at every release, so this is a good heuristic.  Tricky bits: ' returns the name of the last tag with '\n' included,  so we use ' to drop the last character and remove '\n'.  Then, we ask git log  'tag-name..', which is its syntax for  all commits J since a particular tag. In this case, our tag-name is the last tag, so we' re good. KAsk Subversion for changes in general; we accept an options argument which O will be passed onto Subversion, so you can customize by using any of the many  options to  which Subversion understands. 7Nothing fancy: just get the entire repository history.  Unfortunately, Subversion doesn't have a very useful notion of * tags, so we merely get the full history. DAsk CVS for changes in general; we accept an options argument which H will be passed onto CVS, so you can customize by using any of the many  options to changes which CVS understands. # WARNING: This seems to be broken. 7Nothing fancy: just get the entire repository history. JAsk Mercurial for changes in general; we accept an options argument which N will be passed onto Mercurial, so you can customize by using any of the many  options to  which Mercurial understands. 7Nothing fancy: just get the entire repository history. GAsk Mercurial for all changes, since the last tag. Conscientious folks 4 tag at every release, so this is a good heuristic.     FAsk Darcs for changes in general; we accept an options argument which J will be passed onto Darcs, so you can customize by using any of the many  options to changes which Darcs understands. 7Nothing fancy: just get the entire repository history. CAsk Darcs for all changes, since the last tag. Conscientious folks 4 tag at every release, so this is a good heuristic.         change-monger-0.0Text.ChangeMonger.ParseText.ChangeMonger.GitText.ChangeMonger.SubversionText.ChangeMonger.CVSText.ChangeMonger.MercurialText.ChangeMonger.Darcsrun gitChanges gitChangesAllgitChangesSince svnChanges svnChangesAll cvsChanges cvsChangesAll hgChanges hgChangesAllhgChangesSince darcsChangesdarcsChangesAlldarcsChangesSincegitRunbase GHC.FloatlogGHC.ListinitrunHgrelease