Re: bzr repository ready?

["Óscar Fuentes" <ofv@wanadoo.es>]

Lennart Borgman <lennart.borgman@gmail.com> writes:

> Currently I have two checkouts from Emacs CVS:
>
> * One which I just checkout and compile. I upload it if someone wants
> it, but I do not use it - except for bug checking and reporting.
>
> * The second checkout is where I have all my patches. (I have thrown
> away quite a lot of them, it takes too much time to have them and if
> they never makes it into Emacs I can just as well put them in the
> garbage can. That saves me time at least. There are however some small
> patches that are essential to get Emacs working descently.)
>
> I never merge those changes myself into the upstream Emacs becaus I
> have felt to unsure about the operations. That is a pitty of course
> since it causes other people trouble, but ...
>
> From this second checkout I build my patched version of Emacs which I
> myself and many others use.
>
>
> How should I set things up when using bazaar? I would really like to
> somehow have my patches also in a repository an Launchpad. That would
> make many things more simple.

If you were starting from scratch with emacs and bazaar, you clone emacs
development branch (with `bzr branch URL' or downloading a
tarball). This way you have a branch which is your local mirror of
emacs' development and acts as the basis for your experiments.

You are interested on a personal variation of emacs' sources. For this
you clone your local mirror and incorporate your changes, one at a time,
on the new branch. The net effect is as if you were using your own,
private, emacs CVS *repository* which as rich as the GNU one. From time
to time you merge in the changes from the GNU development branch, for
keeping your personal emacs up to date. Finally, you can publish your
personalized emacs branch either directly, from your own machine, or
with some service like launchpad.

The advantage over your actual CVS setup is that you are using the full
capabilities of a VC system for your own convenience, with history,
etc. People can see which changes you made your emacs variation the same
way they can see the changes the rest of developers do to the GNU
branch. This opens a lot of new possibilites. For instance, if I were
tracking the official emacs development, I could create my private
mirror and incorporate specific changes from your branch.

BTW, did you see the e-mail I wrote to you a few days ago asking for the
patch that fixes the maximized frame bug? If we were using bzr right
now, I could locate and incorporate the change on my own emacs branch.

-- 
Óscar