Making bzr commit more like debcommit

[Micah Gersten]

On 01/24/2011 09:54 AM, Barry Warsaw wrote:
> 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

I actually wanted to add more features to debcommit like passing an
author name.  It might be easier to try to standardize on debcommit so
that it's portable across multiple VCSs.  Making bzr commit call
--fixes also sounds good for those that strictly use bzr.

Micah

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-distributed-devel/attachments/20110124/5ee1b61e/attachment.html>