Bazaar-NG traffic #2

[Martin Pool]

Thanks James,

That's a good summary, and interesting to read.
I have a few small corrections.

I would say the big news for this week is that we released 0.1, which has
the upgrade in format.  Having that over is a big relief and we can now
pick up some pending patches and also add new features.

You could also mention UBZ.

I don't know about others but I'd rather be called "Martin".

> = How to do tabs in bzr =

There was discussion of both tabs and tags but they're different things.
> = Terminating with a broken pipe =
>
> In a related sub-thread, Martin Pool followed up on a post about bzr
> complaining about broken pipes when output was fed through programs like
> less. Pool seemed open about whether not to complain about the broken pipe
> and started discussing the issue with David Allouche. They both have
> decided to get rid of broken pipes and are lightly discussing the matter
> for the approach.

We can't get rid of them because we have no choice in whether they
happen; we just decided to suppress the message.

> to do with the new pull --basis (which allows one to use another local
> branch as a cache for the branch you're getting). Apparently the issue gets
> a little more complicated now that weave has been merged into Bazaar-NG.
> Robert Collins reports that Pool is already half-way to solving the problem.
>
> In a related discussion off-list, yours truly learned that --basis is
> currently disabled for the 0.10pre series at least.

This missed the cut for 0.1 but we'll put it back shortly.

> = Bazaar-NG merge can fail =

A better title would be "handling conflicted deleted files".
> = Code Cleanup =
>
> Niemeyer called for the code in Bzr to get cleaned up. Variable names are
> not currently fully consistent (a nightmare for something written in
> python).

I've had worse nightmares.

> He wrapped up with a call to write coding conventions for
> Bazaar-NG. Martin, Meinel and Pool liked the idea and jumped in.
> Eventually, Pool made a HACKING file which was put up on the wiki and in
> the source code.
--
Martin