Skip to content
Commits on Mar 14, 2012
  1. releasing version 1.20120314

    committed Mar 13, 2012
Commits on Mar 13, 2012
  1. really fix

    committed Mar 13, 2012
    This is a crummy way to do it, but I know github library will be switching
    away from conduit, so getting too close to conduit to properly extract
    the http status code seems ill-advised
  2. fix detection of disabled api

    committed Mar 13, 2012
  3. releasing to cabal

    committed Mar 13, 2012
  4. update for github 0.2.1

    committed Mar 13, 2012
Commits on Feb 25, 2012
Commits on Feb 22, 2012
  1. cleanup

    committed Feb 22, 2012
Commits on Feb 15, 2012
  1. @RichiH


    RichiH committed with Feb 15, 2012
    * Use references to actually existing repository
Commits on Feb 1, 2012
  1. no private repos

    committed Feb 1, 2012
  2. also back up organizations by name

    committed Jan 31, 2012
Commits on Jan 31, 2012
  1. relasing to cabal

    committed Jan 31, 2012
  2. typo

    committed Jan 31, 2012
  3. add a summary of failed requests

    committed Jan 31, 2012
    useful for debugging, etc
    Also, simplified the Request type
Commits on Jan 30, 2012
  1. debianization

    committed Jan 30, 2012
  2. update file list

    committed Jan 30, 2012
    I hate file lists that have to be manually updated. Why, cabal, why?
  3. fix committing out of tree

    committed Jan 30, 2012
  4. fix exception handling

    committed Jan 30, 2012
  5. golfing

    committed Jan 30, 2012
  6. add getState too

    committed Jan 29, 2012
  7. figured out the space leak

    committed Jan 29, 2012
    Or rather, Claude Heiland-Allen explained it in
    <> on haskell-cafe.
Commits on Jan 29, 2012
  1. committing bugfix

    committed Jan 29, 2012
    only look at the temp work tree
  2. reorder fetching

    committed Jan 29, 2012
  3. fix memory leak

    committed Jan 29, 2012
    Oddly, re-reading the git config caused a memory leak. Profiling showed
    all memory was being used by list conses. Presumably for the list of
    remotes in the git config. Although it grew too fast to just be that;
    at an increasing rate. My guess is that, somehow, the old git config
    data was retained. However, I cannot see anything that would cause that
    to happen, since the value is stored in the monad. Nothing should refer
    to an old value of that state. Weird.
    Anyway, to fix it, let's just not reread git config. This does mean that
    if github puts in a fork loop, we might go round and round. It also
    complicated fetching from the remotes. Now we fetch when adding a new fork,
    and all the existing forks are fetched from at startup.
  4. smarter wiki adding

    committed Jan 29, 2012
  5. also clone wikis

    committed Jan 29, 2012
    Wikis are git repos, but they have no extra metadata. So just clone them.
    Note that the github api seems to always set has_wiki = True, even when
    a repo really has no wiki. I think this is an api bug. The consequence
    is that wikis are added for every repo, and trying to pull from them
    prints error messages:
    fatal: The remote end hung up unexpectedly
    TODO: suppress those errors
  6. reduce duplication

    committed Jan 29, 2012
Something went wrong with that request. Please try again.