=== jaimef_ is now known as jaimef
=== alpacaherder is now known as skellat
=== alpacaherder is now known as skellat
[12:23] <Munchor> Hi is there a bzr command that prints out every revision number and its commit message on the terminal?
[12:26] <Munchor> oh found it, 'bzr log', thank you
[13:44] <mathrick_> jelmer: so it seems that git dpush retroactively erases file-ids somehow, and makes the tree root be TREE_ROOT. How's that possible at all (I thought file ids were a part of the commit, and thus immutable)?
[14:01] <maxb> Normally yes, but the d in dpush is 'destructive'
[15:44] <mathrick_> maxb: hmm, so it basically replaces the true history with one rebased onto the remote?
[16:48] <jelmer> mathrick_: yes, that's why it's a separate command
[16:49] <jelmer> mathrick_: you can prevent that behaviour with --no-rebase
[16:49] <mathrick_> jelmer: any way to have a tree I push to git and be able to join it with another git-backed tree?
[16:50] <jelmer> mathrick_: I don
[16:50] <jelmer> 't think that works at the moment
[16:50] <mathrick_> damn
[16:50] <jelmer> not without "proper" push support, which I never finished for bzr-git
[16:50] <mathrick_> and "at the moment" seems to be here to stay :\
[16:51] <mathrick_> I really don't want to use git to interact with git trees
[16:52] <jelmer> mathrick_: it'd be great if somebody could take over bzr-git maintenance
[16:52] <mathrick_> jelmer: I don't think I could do it without understanding git really well, which kinda defeats the purpose of using bzr-git to avoid touching git
[16:53] <mathrick_> lemme tell you, the result of DVCS wars don't make me happy a single bit
[16:53] <mathrick_> *results
[16:54] <mathrick_> jelmer: what's lacking in "proper" git push support?
[16:54] <jelmer> support for lots of corner cases
[16:55] <mathrick_> sounds like understanding git very well is mandatory for those
[16:59] <mathrick_> jelmer: another thing, which is very hard to glean, is there anyone doing anything at all with bzr still? I know that the canonical team has been effectively disbanded, but do you have any idea if anyone remains working on it in spare time, or if anyone from the outside came?
[17:02] <mathrick_> to be honest, it's not even possible to guess, without some very extensive googling, that the project is effectively dormant
[17:16] <jelmer> mathrick_: yes, hacking on bzr-git requires knowledge of both bzr and git internals
[17:17] <jelmer> mathrick_: there isn't really a way around that :-)
[17:17] <jelmer> I think the commit logs, the bug tracker and the mailing list archives show a correct picture
[17:17] <jelmer> bzr isn't dead - there are still things happening - but at a rate that's much lower than before
[18:37] <SamB> wow, there seem to have been several commits to lp:bzr in may
[18:41] <Jayden> Hi all.  I just started using bzr ... to checkout the src to a project I'm interested in (fwiw, MariaDB).  I'm having a heck of a time checking-out the entire repo; keep getting "Connection Timeout: disconnecting client after 300.0 secondse 1178175/1178175" at various points/times.
[18:42] <Jayden> Is there a 'resume' command in bzr? Starting over each time is getting me nowhere fast.
[18:46] <SamB> -r might help?
[18:48] <SamB> like, start with -r 100 and then pull with gradually increasing numbers
[18:49] <Jayden> SamB: Hi.  How would pulling a specific revision help?
[18:52] <Jayden> ah, missed your comment.  I suppose that could work; worth a try.
[18:56] <Jayden> SamB_: Looks like a working, if clunky, solution.  Thanks!
=== marcoceppi_ is now known as marcoceppi
=== SamB_ is now known as SamB