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

[CHENG Gao <chenggao@gmail.com>]

*On Sat, 8 Aug 2009 20:51:31 +0200
* Also sprach B Smith-Mannschott <bsmith.occs@gmail.com>:

> On Sat, Aug 8, 2009 at 18:24, Bastien<bastienguerry@googlemail.com> wrote:
>> Can someone describe the bzr workflow for Emacs developers?
>
> Presumably, you've seen this, yes?:
> http://www.emacswiki.org/emacs/BzrForEmacsDevs

Thank you for the info. It's great as a starter guide.

I am trying to follow it to set up using unofficial Emacs bzr repo at
http://bzr.notengoamigos.org/emacs/trunk/.

But to be honest, it's fairly painful.

On Aug. 1 I did "bzr branch", and I recorded the result as below:

,----
| $ time bzr clone http://bzr.notengoamigos.org/emacs/trunk/ emacs
| Branched 95203 revision(s).                                                                                                        
| 
| real	193m58.965s
| user	6m58.284s
| sys	1m12.954s
`----

I just did "bzr pull" and found it's fairly slow. I did not time it.

Now I am following the above mentioned BzrForEmacsDevs guide to make a
local dev branch. Very slow.

I am using Bzr 1.17 on MacOSX.


>
>> Will the switch to bzr affect the way upstream packages like Gnus
>> or Org are integrated in Emacs development?
>>
>> Would there be any advantage of switching to bzr for these packages?
>
> Well, the wiki page currently only says:
>
> [quote]
> Merging Upstream Packages (e.g., Gnus) Into Emacs With Bazaar
>
> TODO: TBD (but frankly, this should be easy, as it fits perfectly with
> the DVCS/Bazaar model anyway)
> [/quote]
>
> // ben
>
>
>