Changing a commit message

Raúl Núñez de Arenas Coronado raul at dervishd.net
Thu May 15 09:18:50 BST 2008


Saluton TPJ :)

On Thu, 15 May 2008 08:18:30 +0200, TPJ dixit:
> > (Raul Nunez wrote:)
> > Well, depending on the project I may want centralized workflow and
> > full control over my project, so then modifiable commit messages
> > would be really great, but on the other hand I switched to Bazaar
> > from Subversion because the decentralized workflow, I don't want
> > "master" branches, so although I would really love modifiable commit
> > messages, I think that they may be more a harm than a good for
> > distributed projects.
> 
> I think we still talk about different things...
> 
> To make myself clear: I don't want to force anyone who uses Bazaar in
> a decentralized workflow to allow commit messages changes. I just want
> to make it possible to change commit messages in *centralized* Bazaar
> workflows.

But with Bazaar you can go from centralized to decentralized at any
point, using a branch that allowed commit messages as the parent branch.

> On the other hand, if I want a centralized workflow, I could create my
> repository like that:
> 
> $ bzr init-repo --no-trees --allow-commit-messages-changes <location>
> 
> So, we both could be happy with the same Bazaar!

Until I do "bzr branch <location" and start to work decentralized... and
I distribute my branch (I push it to a public location). Then my branch
will be decentralized *and* will allow modified commit messages. Again,
propagation problems, database issues, etc.
 
For this to work, repos with "--allow-commit-message-changes" would have
to be locked (e.g., non branchable). Those branches should never go
distributed.

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 ...



More information about the bazaar mailing list