Partial fix for "null" `HGChangeset` "null" changeset is currently kept as a singleton instance, i.e., `HGChangeset null` always return the same object. However, some queries (such as `#isObsolete` or `#successors`) require repository to be set - obviously, for "null" changeset there's no repository. Therefore these queries resulted into DNU. To paetially fix this, short-circuit these query methods to answer trasonable values for "null" changeset. Better solution would be to make "null" changeset a normal changeset within a repository.

2014-03-05 Jan Vrany <jan.vrany (o) fit.cvut.cz>

  * Fixed handling of circular class renames (issue #18)
  * Improved support for nested packages (issue #29)


2013-07-19 Jan Vrany <jan.vrany (o) fit.cvut.cz>

  * Initial release of stx:libscm 1.0