"Committing to: ..." message should include thread name

[Andrew Bennetts]

It would be good if "bzr commit" in a thread reported which thread it was committing to. bzr itself already reports which branch it is committing to, this is just an extension of that.

At the moment the output looks like:

$ bzr ci -m "Fix test failures."
Committing to: /home/andrew/warthogs/bzr/push-improvement-loom/
modified bzrlib/tests/test_selftest.py
Committed revision 3467.

I would like something more like:

Committing to: 'old-hpss-branch-implementation-test' in /home/andrew/warthogs/bzr/push-improvement-loom/
modified bzrlib/tests/test_selftest.py
Committed revision 3467.

The reason why this is useful is that if a commit is made in the wrong location, then it immediately becomes obvious, which allows the user to uncommit immediately to undo the mistake (and prevents them from unknowingly doing further commits on the wrong thread).

[Robert Collins (lifeless)]

 importance medium
 status triaged

[John A Meinel (jameinel)]

As an interesting workaround, you might configure your shell to show you "bzr nick" of where you are working. Because that will show you the name of the loom you are working on. You can do it in bash with something like:

PS1='\u@\h \w {$(bzr nick 2>/dev/null)}\n\$ '

That gives a 2-line prompt which looks like:

jameinel@host ~/working/directory {nick}
$ <your command here>

I have mine tweaked a bit to not show nick if I'm not in a directory, and to color the whole thing as I like it.

That would actually give you the information *before* you commit, rather than after.

Just a thought.

[Andrew Bennetts (spiv)]

John, that is an interesting workaround. In my case I'd want it to not show the nick if the branch wasn't a loom, or perhaps just if the nick is different to the basename of the branch root directory.

Fixing this bug would wholly satisfy me though, without the need to clutter my prompt or to figure out the right magic incantations to do so efficiently :)