Changeset comments for non-committed files are lost on commit

[Sven Sandberg]

I have a source tree with two changed files: file1 and file2.
I use 'bzr gci' and type in changeset comment for each of them.
Then I decide I want to commit them as two different changesets, so I uncheck file2 and commit file1.
Then the changeset comments for file2 are lost.

Since we have the nice feature that changeset comments are saved when a commit is cancelled, it would be better if we could also save changeset comments for files that are not committed.

(This is a bigger issue when you have 100 files in each of the commits.)

Workaround:
(1) Make a full commit of all files.
(2) Make a new branch. Call the two branches b1 and b2. In both b1 and b2, the top changeset now contains both file1 and file2.
(3) Uncommit in both b1 and b2 (the changeset comments are saved).
(4) In b1, commit only file1.
(5) In b2, pull from b1.
(6) In b2, commit again. Now only file2 is included in the commit, and it has the correct changeset comment.

[Jelmer Vernooij (jelmer)]

We should really move the per-file commit message code into bzr core or a separate plugin rather than bzr-gtk.