| james_w | what would be the old way of spelling Graph.iter_lefthand_history()? | 03:48 |
|---|---|---|
| lifeless | branch.get_history(0 | 03:54 |
| AfC | I lament Git. | 05:07 |
| poolie | mm | 05:34 |
| twb | bzr-fastimport repo used to include darcs-fast-export script. Now I can't find it. What happened to it? | 06:51 |
| twb | Hmm, seems latest version simply delete all exporters, without telling me where to get replacements | 06:52 |
| * twb randomly googles and finds http://hackage.haskell.org/package/darcs-fastconvert | 06:54 | |
| mgz | morning | 09:12 |
| johan | Hi, I'm having an issue uncommiting a set of changes in a branch, using bzr 2.5.0 | 11:45 |
| johan | bzr: ERROR: An inconsistent delta was supplied involving 'pixmaps/validation-error-16.png', 'pixmapsvalidationerr-20070828004315-ef6og11rrm2qvq9v-234' | 11:45 |
| johan | reason: Unable to find block for this record. Was the parent added? | 11:45 |
| johan | happens when I try to uncommit | 11:45 |
| mgz | johan: similar to bug 910002 maybe? | 11:47 |
| ubot5 | Launchpad bug 910002 in Bazaar "uncommitting a dir rename causes InconsistentDelta error" [High,Confirmed] https://launchpad.net/bugs/910002 | 11:47 |
| johan | mgz: yes, seems to be the same issue | 11:48 |
| johan | running bzr uncommit again says nothing to commit, but it also complains that the working tree needs to be updated | 11:49 |
| johan | I'd really like to be able to check out an earlier version of a branch before that bug is fixed | 11:49 |
| mgz | you can just do that | 11:50 |
| mgz | `bzr co --lightweight -r -5 ../olderversion` for instance | 11:51 |
| johan | ah, let me try that | 11:51 |
| mgz | plus the . to indicate from the cwd | 11:51 |
| johan | not needed, it worked fine thanks | 11:52 |
| hypnocat | bzr is often criticised for being slow compared to git.. is bzr slow because it's written in python? or because of the algorithms it uses? or some design decisions? | 14:31 |
| mgz | it's mostly historical | 14:33 |
| mgz | git was born fast and dumb, bzr evolved differently | 14:34 |
| quicksilver | git was designed pretty much first and foremost "how do I maintain linux kernel source trees and fast" | 14:35 |
| mgz | so, many core things these days don't have very different performance characteristics | 14:35 |
| quicksilver | and since the linux kernel tree is (a) big and (b) had loads of history | 14:35 |
| quicksilver | actually having a design that made sense was quite secondary to it being very fast. | 14:35 |
| quicksilver | bzr was designed "how do we do DVCS right?" | 14:36 |
| johan | no history was imported into the kernel when git was created | 14:36 |
| quicksilver | really? I stand corrected. | 14:36 |
| mgz | there are still some obvious differences | 14:36 |
| johan | they left the old bitkeeper data behind and did a clean break | 14:36 |
| mgz | cold startup is worse with python | 14:37 |
| hypnocat | would it help if bzr used one of the python compilers instead of the python interpreter? | 14:37 |
| mgz | so, your first vcs command after a memory pressure situation will be faster with a small binary rather than lots of pyc files | 14:38 |
| mgz | hypnocat: no, in short. | 14:39 |
| mgz | long version, bzr already uses cython (and C) for some parts where more C-like performance is needed | 14:40 |
| mgz | and the pypy answer to bad performance is "let it run for several seconds so the JIT warms up" | 14:40 |
| mgz | which obviously doesn't help much with a multiply invoked commandline tool like bzr | 14:41 |
| hypnocat | so, what are the main things that bzr does right compared to git that slow it down so much? | 14:41 |
| mgz | I think you missed my first line :) | 14:41 |
| hypnocat | that it's historical? | 14:41 |
| hypnocat | i got that.. they evolved differently | 14:42 |
| hypnocat | and the core stuff has similar performance | 14:42 |
| mgz | these days, there aren't big differences in performance on basic opterations | 14:42 |
| hypnocat | so where are the big performance differences? | 14:42 |
| mgz | I think their network protocol is more reliably performant | 14:43 |
| mgz | because there's only one way of doing it, whereas bzr doesn't discourage you from using lots of different protocols, some of which then do silly things | 14:44 |
| mgz | feel free to benchmark things though, or look in the list archives for older benchmarks, a few have been done | 14:48 |
| hypnocat | alright, thank you | 14:48 |
| === Quintasan_ is now known as Quintasan | ||
| === yofel_ is now known as yofel | ||
| === deryck is now known as deryck[lunch] | ||
| bsd | Hi jelmer. Is there any support in bzr-svn (or a bug) to allow stacking against a Subversion repo? I'm having to work against a very large and old repo, and it will take days (weeks!) to download it all… | 18:38 |
| jelmer | hi bsd | 18:38 |
| jelmer | bsd: unfortunately stacking across different repository formats is not supported at the moment, and the svn format does not support stacking itself | 18:39 |
| bsd | jelmer: so there's little that can be done other than maintaining a parallel branch. Oh well. | 18:42 |
| === deryck[lunch] is now known as deryck | ||
| jelmer | bsd: how big is the branch? | 18:44 |
| bsd | jelmer: 142k entries. But they've pushed in zip files and all sorts of monstrous binaries. | 18:44 |
| jelmer | ah | 18:44 |
| === Omni|AFK is now known as Omni|Work | ||
| Omni|Work | How do I find out which branch a tag is on? | 20:34 |
| Omni|Work | I do 'bzr tags' and there are a whole ton of tags with a '?' on them. | 20:34 |
| wilx | The information is part of the log output. | 20:35 |
| * Omni|Work nods. | 20:45 | |
| poolie | hi all | 23:13 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!