[Maria-developers] Updated (by Guest): Table elimination (17)

--- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...: Table elimination CREATION DATE..: Sun, 10 May 2009, 19:57 SUPERVISOR.: Monty

Re: [Maria-developers] Bzr merge order

Hi! Kristian == Kristian Nielsen kniel...@knielsen-hq.org writes: K Following up on this, I just learned about the bzr option K append_revisions_only that can be set on a branch. K This option can be used to enforce that the main history (sequence of K primary/left-hand parents from the tip)

Re: [Maria-developers] Bzr merge order

Hi! Kristian == Kristian Nielsen kniel...@knielsen-hq.org writes: Kristian Kristian Nielsen kniel...@knielsen-hq.org writes: Following up on this, I just learned about the bzr option append_revisions_only that can be set on a branch. Kristian Any opinions on this? Kristian Having thought

Re: [Maria-developers] Bzr merge order

Michael Widenius mo...@askmonty.org writes: K In this case, Joe will instead have to do this: K bzr branch lp:maria # or bzr pull lp:maria into an existing clean clone K bzr merge ../branch-with-patch K bzr commit -mmerged with trunk K bzr push lp:maria K Then the

[Maria-developers] Updated (by Guest): index_merge: fair choice between index_merge union and range access (24)

--- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...: index_merge: fair choice between index_merge union and range access CREATION DATE..: Tue, 26