=== Spads_ is now known as Spads [12:35] GAHHH [12:36] ONCE AGAIN bzr up did not abort on diverged history but instead made a merge [12:36] How do I a) unfuck this, and b) stop it EVER doing it again? [12:36] I do not *EVER* want bzr up to merge. if there's divergant history I want it to complain, so that I can rebase [12:58] LeoNerd: so bzr up kind of *is* merge [12:59] Yes. I don't want one [12:59] so why did you run bzr up, exactly? [12:59] I want it to bring me in new non-divergent history, or abort if there is [12:59] are you doing a bzr checkout? [12:59] It's a checkout yes [13:00] is there a reason you're doing that instead of bzr branch? [13:00] Because most of the time I'm online and therefore I want to use the central server [13:00] the semantics of bzr checkout are there to support people who are uncomfortable with anything but SVN, near as I can tell [13:00] everyone else just uses bzr branch [13:00] and does pull/merge/push [13:00] a pull will abort on divergent history [13:01] up is basically "merge from where I checked out to" and that is basically all it is [13:02] s/ to// [13:02] Ah; maybe I should just use pull then..? [13:03] I think so [13:03] you'll need to branch first [13:03] Nah [13:03] your checkout has no repo basically [13:03] pull :bound == up, give or take [13:03] yeah [13:03] see this conflict detection is a repo opration [13:03] mostly [13:03] so it's about two repos communicating [13:03] (I think) [13:03] so a branch will have a local repo [13:04] and can thus negotiate the conflicts correctly [13:04] but if pull :bound works, then do use it! [13:04] but divergent history vs :bound doesn't make sense to my mind [13:04] history only exists in branches [13:04] not checkouts [13:04] checkouts defer history to the bound branch [13:04] I only really get divergent history if I was offline on my laptop, like on a train [13:04] As happened here [13:04] if you're doing work offline on your laptop, you want to branch locally [13:05] unless this is something pathological like a repo with 44G of history or something [13:05] Hrm? A checkout is a branch [13:05] not really [13:05] bzr co == bzr branch + bzr bind [13:06] hm [13:06] It's not a _lightweight_ checkout.. it still has a local branch [13:06] ahhhh [13:06] okay sorry [13:06] yes, I was thinking lightweight [13:06] :) [13:06] so yeah, see if pull :bound has the right semantics for you [13:06] Oh, Ialready know it does. I just keep forgetting to do that [13:06] heh [13:06] ((You only need :bound the first time; it'll remember afterwards) [13:06] bzr pull --remember is handy when you get those wrong [13:08] maybe bzr alias up="pull :bound" would help :) [13:08] * Spads does that on his one heavyweight checkout [13:11] * Spads has been using bzr since 2006 or so, and could swear that bzr co used to do lightweight checkouts [13:12] Mm... I don't think it ever has done [13:12] Though that might be a configurable option [13:14] iinteresting [13:14] TIL [17:51] Your problem isn't using 'up', it's using 'ci --local'. I still maintain that its existence is a bug :p