Changing a commit message, upgrading from -subtree formats

[Raúl Núñez de Arenas Coronado]

Hi all :)

I'm new to the list and relatively new to Bazaar: I'm using it since
version 0.90 and I've moved all my projects to it, but I don't use all
the capabilities (yet).

Right now I only have two problems with Bazaar. First one regards
commit messages. I've noticed a couple of commit messages in some of my
projects containing typos or a horrible redaction, and I would like to
change them. Using a non-distributed VS like Subversion, I achieved
that using "svn-admin" and changing the log message in the repository,
but since Bazaar is distributed, there is no "master" copy to be
modified. I know that, but let's assume that the branch I have at place
X is the master branch and everybody branches, merges and checkouts
from it. So, how could I change a commit message in that branch? Would
everyone get the new message if branching, updateing, pulling or
merging from my branch or do they have to specify the exact
revision whose message got changed?

So far the only way of changing the message I can think about is
branching the offending revision, uncommiting it, fixing, commiting and
merging, but that is a bit of a mess because I want the revision
history as unchanged as possible (so I would prefer to avoid merges).
https://answers.launchpad.net/bzr/+question/32097 is another way, but
does not work without the rebase plugin and I don't know if it is a
good way of doing what I want.

My question is not related with
https://answers.launchpad.net/bzr/+question/19300 since I've made many
commits after the offending revision, not only one.


The second question is regarding -subtree formats. A friend of mine and
me converted some projects from SVN to Bazaar using bzr-svn and the
imported branch had format "dirstate-with-subtree". This is a hidden
format, and we would prefer to use pack-0.92. Unfortunately, "bzr
upgrade" doesn't work from -subtree formats, no matter if you use
subtrees or not (we don't, and as far as we know, our SVN repos didn't
make use of "svn:external", so the imported branch shouldn't use nested
trees, either). Apart from the obvious solution of creating a new
branch in pack-0.92 format and going revision by revision duplicating
the changes to the newly created branch (bzr diff in branch with
subtree, patch the new branch, commit in new branch), I can think of
any good solution to this problem. Any ideas? Will Bazaar 1.5 address
this problem?

Well, that's all, thanks a lot in advance and thanks for Bazaar!

Raúl "DervishD" Núñez de Arenas Coronado
-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
We are waiting for 13 Feb 2009 23:31:30 +0000 ...