= Limitations of Monotone =

This page lists limitations of monotone which will affect Pidgin developers, as well as known workarounds and upstream status.  It is not intended to be a monotone bug tracker, but rather a place to gather high-priority problems which we might want to either work on in monotone or bring to the attention of the regular monotone developers.

 * '''No workspace merge''' - The inability to perform logical fixups at merge-time (only conflict fixups) introduces a glitch into our traditional "Pidgin should always compile" philosophy.  While we recognize that a DVCS may require some workflow changes, this isn't one we're ready to give up on, yet.
 * '''{{{annotate}}} and {{{log <file>}}} speed''' - Particularly while we are validating the svn import, these are noticable limitations.  Work is underway upstream to mitigate these, in the form of "heights".  See [Monotone:RevisionNumbering] for some details; one of those heights proposals has been accepted, and a faster {{{log <file>}}} will be in the 0.32 release.  {{{annotate}}} remains in a branch.
 * '''Partial Pull''' - Complete (initial) pulls of Gaim are ~1h on a fast connection.  This is too long to expect any casual developer to invest.