[ANN] bzr-2.5b6 has been frozen !

Martin Packman martin.packman at canonical.com
Fri Feb 3 15:12:12 UTC 2012

On 03/02/2012, INADA Naoki <songofacandy at gmail.com> wrote:
> Is this mean there are no more chance to land my merge request(*)?
> *)
> https://code.launchpad.net/~songofacandy/bzr/user_encoding_utf8/+merge/90039

Sorry Naoki, things were a little confused by reusing the same merge
proposal for the more limited change, so it wasn't clear it still
needed handling. I think this kind of thing can still go into 2.5
final depending on how the other changes to encoding handling play

I'm looking at more specific changes in several areas which should
make defaulting to utf-8 globally less desirable. Your example issue
in the earlier mailing list thread, with interpreting the commit
message from an editor when LANG=C, is much the same as bug 610229.
Just changing the user encoding in some circumstances is not a
complete fix for that.

However, if there are too many things left to address on this front
for the 2.5 release, landing your branch there may be the easiest way
to make LANG=C environments less surprising.


More information about the bazaar mailing list