Re: Switching to bzr: what Emacs developers should know?

[Stefan Monnier]

>> Can someone describe the bzr workflow for Emacs developers?
> Presumably, you've seen this, yes?:
> http://www.emacswiki.org/emacs/BzrForEmacsDevs
>> Will the switch to bzr affect the way upstream packages like Gnus
>> or Org are integrated in Emacs development?

Of course.  Gnus is the special one because it currently benefits from
a very nice setup.  For Org, I don't think it can get much worse.

>> Would there be any advantage of switching to bzr for these packages?
> Well, the wiki page currently only says:

> TODO: TBD (but frankly, this should be easy, as it fits perfectly with
> the DVCS/Bazaar model anyway)

Actually, for Gnus it seems not particularly easy, because two-way
merges like those Miles currently does don't seem to fit into the Bazaar
model nicely at all and because merging two separate package histories
into one seems to fit even worse.


        Stefan