| 262 | | == Bugs and Limitations == |
| 263 | | |
| 264 | | There are still a lot of things that can be improved. |
| 265 | | |
| 266 | | === Features that Trac+svn has but not currently implemented for Trac+hg === |
| 267 | | |
| 268 | | * ~~History doesn't follow copy/move operations~~ ''implemented in r8445'' |
| 269 | | [[br]] |
| 270 | | Works for files only, which is OK I think, as Mercurial has no notion of directories |
| 271 | | and detecting copy/move of directories would be pretty hard to implement |
| 272 | | * No ''path history'' mode (i.e. show all create/delete operations that |
| 273 | | affected a given path) |
| 274 | | * ~~Revision log ranges [xxx:yyy]~~ ''implemented in r10427 for Trac [milestone:0.12.2]'' |
| 275 | | * ~~View arbitrary diffs~~ ''implemented in r6053'' |
| 276 | | |
| 277 | | === Multi-repository support === |
| 278 | | |
| 279 | | First and foremost, even if Mercurial allows intra-repository branching, |
| 280 | | it strongly supports the use of branching by cloning the full repository. |
| 281 | | Therefore, it is common to have a lot of hg repositories around, each |
| 282 | | devoted to the implementation of some particular feature. |
| 283 | | |
| 284 | | Trac should support this by the way of multiple repository support |
| 285 | | within a single environment (see #2086). |
| 286 | | |
| 287 | | This is now implemented since Trac [milestone:0.12]. Use the 0.12 version of the plugin. |
| 288 | | |
| 289 | | |
| 290 | | === To cache or not to cache? === |
| 291 | | |
| 292 | | Recent versions of the plugin (r7744 for 0.11 or r7757 for 0.12) have a greatly improved browsing speed. It's now possible to navigate on repositories of the size of the Linux kernel repo. |
| 293 | | |
| 294 | | However, producing diffs or even gathering the timeline events for repositories of such size is still too slow. |
| 295 | | For the diffs, we could reduce the amount diffs generated (see #2591, #7975). |
| 296 | | For the timeline, we should really have a cache, not only for the performance issue but also because the current heuristic for retrieving the changesets in a given period of time doesn't always work (see r5365). |
| 297 | | |
| 339 | | |
| 340 | | == Troubleshooting == |
| 341 | | |
| 342 | | === "unsupported version control system hg" === |
| | 303 | [[TicketQuery(component=plugin/mercurial,milestone=plugin - mercurial,status=!closed,type=enhancement)]] |
| | 304 | |
| | 305 | |
| | 306 | == Bugs and Limitations == |
| | 307 | |
| | 308 | There are still a lot of things that can be improved. |
| | 309 | |
| | 310 | === Features that Trac+svn has but not currently implemented for Trac+hg === |
| | 311 | |
| | 312 | * No ''path history'' mode (i.e. show all create/delete operations that |
| | 313 | affected a given path) |
| | 314 | |
| | 315 | === To cache or not to cache? === |
| | 316 | |
| | 317 | Recent versions of the plugin (r7744 for 0.11 or r7757 for 0.12) have a greatly improved browsing speed. It's now possible to navigate on repositories of the size of the Linux kernel repo. |
| | 318 | |
| | 319 | However, producing diffs or even gathering the timeline events for repositories of such size is still too slow. |
| | 320 | For the diffs, we could reduce the amount diffs generated (see #2591, #7975). |
| | 321 | For the timeline, we should really have a cache, not only for the performance issue but also because the current heuristic for retrieving the changesets in a given period of time doesn't always work (see r5365). |
| | 322 | |
| | 323 | === Troubleshooting |
| | 324 | |
| | 325 | ==== "unsupported version control system hg" |
