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

[Stefan Monnier <monnier@IRO.UMontreal.CA>]

> Is Gnus just in a separate CVS repository right now, and all the changes
> get copied over in some primitive, history-destroying way when a new
> Gnus is put into the Emacs distribution?

Currently Gnus has its own CVS repository and the two repositories are
sync'd two-ways by Miles via Arch mirrors.

> If so, the Bright Shining Future would be to simply version Gnus
> within the Emacs tree, and have the Gnus developers maintain their own
> long-lived branches, just as with anything else.  They don't have to
> make changes outside the Gnus area when they don't want to, after all.

For their own branches, everything is fine and solutions are easy to
find, but for the branches that are shared with Emacs, it's more
delicate: the layout between Emacs and Gnus is different, some of the
files are different, but we want changes made in either repository to
appear in the other.

This same problem appears with several other packages that are
maintained outside Emacs, tho Gnus is the only one to currently benefit
from a really nice solution.  So a good solution to this problem would
be useful for more than just Gnus.


        Stefan