=== _thumper_ is now known as thumper | ||
quotemstr | Dammit, why does bzr fast-export -r date:2012-01-01-revno:-1 onlyexport one revision? | 02:54 |
---|---|---|
quotemstr | Oh. ... | 02:55 |
=== iBasic is now known as BasicOSX | ||
jimis | bzr log -l N -rbranch:../repo/branch | 06:10 |
jimis | no matter how big N is I always get only last log message | 06:10 |
jimis | should I report a bug? | 06:11 |
fullermd | Isn't that exactly what you'd expect? | 06:20 |
fullermd | (well, I mean, obviously not, or you wouldn't bring it up. But it's what _I_'d expect :) | 06:27 |
fullermd | I'd always expect `bzr log -r X` to show exactly one thing; the log message for whatever revision 'X' evaluates to. | 06:28 |
fullermd | And for X == 'branch:/where/ever', that would be the head rev of the branch at /where/ever. | 06:29 |
jimis | fullermd: oh, and how to get the log from another branch? | 06:29 |
jimis | I 'm used to using -rbranch for that | 06:30 |
jimis | (for everything else besides log that is) | 06:30 |
fullermd | Mmm, it's probably not meaning exactly what you think it's meaning on those cases either. But anyway. | 06:30 |
=== spm is now known as stevemci | ||
fullermd | Log takes a path, so just `bzr log /where/ever` would be what you'd want. | 06:31 |
=== stevemci is now known as spm | ||
jimis | fullermd: perfect! thanks :-) | 06:31 |
mgz | morning | 08:06 |
=== yofel_ is now known as yofel | ||
=== lamont` is now known as lamont | ||
=== sideffec1 is now known as sideffect | ||
TJ- | Using bzr 2.5.1 on Ubuntu 12.0 amd64. Branched an Ubuntu project (bzr branch lp:ubuntu/precise-updates/gnome-control-center), wrote a patch, push it to my own LP account (bzr push lp:~tj/gnome-control-center/fix-979959).. The entire local repo is being pushed, but I thought - when branching from LP - my push should only contain my diff (assumed the LP server clones the original branch locally). Am I misunderstanding 'push' in this scenario? | 16:29 |
TJ- | *Ubuntu 12.04 | 16:29 |
mgz | TJ-: if you're basing off the ubuntu branch, you need to push to that project, not the base one | 16:38 |
TJ- | mgz: Ahhhh OK! I somehow had got the impression even for a clone it'd do a lightweight branch on the server to save bandwidth and storage. | 16:39 |
mgz | so, lp:~tj/ubuntu/precise-updates/gnome-control-center/fix-979959 | 16:40 |
mgz | otherwise you stack on the wrong thing, which means you push all the ubuntu related revs along with your change | 16:40 |
TJ- | mgz: Unfortunately using the same path to push to my own account fails. I'll just have to live with pushing the entire repo I guess. | 16:41 |
mgz | TJ-: did you try the location I just gave? if so, can you paste the error in here? | 16:42 |
TJ- | mgz: bzr: ERROR: Permission denied: "~tj/ubuntu/precise-updates/gnome-control-center/fix-979959/": : No such distribution series: 'precise-updates'. | 16:42 |
TJ- | mgz: I also tried it with "precise" and without "ubuntu" and so on | 16:42 |
mgz | TJ-: try just precise rather than with -updates | 16:42 |
mgz | darn. | 16:42 |
TJ- | mgz: hold that!... | 16:43 |
mgz | I think precise should work, I'm not sure how they arrange the updates bits generally. | 16:43 |
TJ- | mgz: that appears to be working... but it is still sucking out all the bandwidth.. says "Fetching revisions" would that be expected? | 16:44 |
TJ- | mgz: I need to check my bash history I must have typoed when I tried just "precise" earlier :O | 16:45 |
mgz | ideally not, but there may still be a large delta | 16:45 |
TJ- | mgz: OK *blush* here's why it failed earlier: "bzr push lp:~tj/precise/gnome-control-center" | 16:45 |
mgz | :) | 16:45 |
TJ- | mgz: by 'delta' you mean my changes versus the origin? One 60 line diff. | 16:46 |
mgz | but we're basing it on the precise branch, there may also be other changes in precise-updates | 16:47 |
TJ- | mgz: OK, that was why I asked the question, so the delta is precise > precise-updates -> my patch | 16:48 |
TJ- | mgz: thank-you so much. I'm a hardcore git user and bazaar still confuses me especially with the launchpad integrations | 16:48 |
quotemstr | Why does "bzr branches" come up with "* (default)"? | 16:50 |
mgz | because you're on a branch without colocated branches underneath I guess | 16:53 |
mgz | what do you expect it to print? | 16:53 |
quotemstr | git-bzr uses bzr branches to get a list of branches. | 16:59 |
quotemstr | When it feeds '*' to the shell, Bad Things happen. | 16:59 |
mgz | * denotes active in `git branch` output no? | 17:00 |
quotemstr | Did the format change recently? | 17:00 |
mgz | probably with the colocated things for 2.5, or perhaps in a more recent 2.6 change | 17:01 |
=== deryck is now known as deryck[lunch] | ||
quotemstr | Are you guys planning on fixing https://bugs.launchpad.net/bzr/+bug/541626 ? | 17:44 |
ubot5 | Ubuntu bug 541626 in Bazaar "'BTreeBuilder' object has no attribute '_find_ancestors'" [High,Confirmed] | 17:44 |
=== deryck[lunch] is now known as deryck | ||
Noldorin | back | 18:23 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!