On Fri, Feb 26, 2010 at 4:19 PM, Sergei Golubchik wrote:
> Eh, you omitted lots of crucial details here, but luckily you mentioned
> them in your email to internals, so I was able to decrypt the above :)
>
> Anyway, what happens - you are not merging one mysql branch into
> another. You merge two
On Fri, Feb 26, 2010 at 6:36 AM, Sergei Golubchik wrote:
> When done, you'll still have your patches on top of the tree, and you
> can trivially extract them (e.g. with bzr log -p) and publish them.
> If you merge instead of rebasing, you'll have old patches in the tree
> and merge changes spread
On Fri, Feb 26, 2010 at 6:36 AM, Sergei Golubchik wrote:
> Hi, MARK!
>
> On Feb 25, MARK CALLAGHAN wrote:
>>
>> I know this question is more about official MySQL than MariaDB, but it
>> is also about sharing code we write at Facebook and all of the patches
>> we publish can be reused by others as
At file:///Users/hakan/work/monty_program/mariadb-tools/
revno: 11 [merge]
revision-id: ha...@askmonty.org-20100226170755-uucbsqe4n60b50c1
parent: ha...@askmonty.org-20100226162413-118168qx5c9c02ml
parent: kniel...@hasky-20100223074854-m
At file:///Users/hakan/work/monty_program/mariadb-tools/
revno: 10
revision-id: ha...@askmonty.org-20100226162413-118168qx5c9c02ml
parent: ha...@askmonty.org-20100219052704-8nnlzsbu0nslnxba
committer: Hakan Kuecuekyilmaz
branch nick: ma
On Fri, Feb 26, 2010 at 1:30 AM, Sergei Golubchik wrote:
> Hi, MARK!
>
> On Feb 25, MARK CALLAGHAN wrote:
>>
>> One other comment. I don't think the official releases are in
>> launchpad. If they were I imagine this would be easier to do. Of
>> course, anyone could republish the official releases
6 matches
Mail list logo
