Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Dec 17, 2006, 7:52:33 PM (17 years ago)
- Author:
-
elb
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v1
|
v1
|
|
| | 1 | = Limitations of Monotone = |
| | 2 | |
| | 3 | 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. |
| | 4 | |
| | 5 | * '''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. |
| | 6 | * '''{{{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; I think this is either in or will be in soon (0.32?). |
| | 7 | * '''Partial Pull''' - Complete (initial) pulls of Gaim are ~1h on a fast connection. This is too long to expect any casual developer to invest. |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!
