Making bzr commit more like debcommit

[Barry Warsaw]

We have 'bzr commit' and we have 'debcommit'.  Currently, the UDD guidelines
talk about both, but for consistency, I'd like to standardize on recommending
'bzr commit'.  One feature that debcommit has:

DEBCOMMIT(1)                                                     DEBCOMMIT(1)

NAME
       debcommit - commit changes to a package

...

VCS SPECIFIC FEATURES
...
       bzr If the changelog entry used for the commit message closes any bugs
           then --fixes options to "bzr commit" will be generated to
           associate the revision and the bugs.

I know we can just do 'bzr commit --fixes lp:12345', though I often forget to
do that until after my last commit, so I tend to add --unchanged, which leads
to an empty revision.

What do you think about making 'bzr commit' act more like debcommit when
there's a new debian/changelog entry?

-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-distributed-devel/attachments/20110124/48b0c101/attachment.pgp>