allow users to force an empty commit message

Bug #172506 reported by Martin Pool
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Low
Unassigned
Nominated for 1.2 by Michael Allman
Nominated for Trunk by Michael Allman

Bug Description

Bazaar currently refuses outright to commit with an empty commit message. It should probably instead just seek confirmation if the editor leaves an empty message, and just give a warning if -m or -F is used.

Tags: commit
Martin Pool (mbp)
Changed in bzr:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Michael Allman (msa-allman) wrote :

Implementation idea #1: make empty commit messages a bazaar.conf option, e.g. "allow_empty_commit_message = (true/false)".
Implementation idea #2: prompt user to continue or abort the commit if an empty commit message is supplied, along the lines of Subversion.

Jelmer Vernooij (jelmer)
tags: added: commit
Revision history for this message
Adam Porter (alphapapa) wrote :

Sometimes I really don't have anything to say about a commit. For example, in a personal repository of documents that I commit once-in-a-while, I may have nothing to say other than "added file". But that's pointless, because bzr already indicates that. Why should I be forced to?

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 172506] Re: allow users to force an empty commit message

@Adam this is probably pretty easy to fix; if you'd like to try we will help

Revision history for this message
Adam Porter (alphapapa) wrote :

Haha, ok, I'm starting to dabble in Python a little. I may have some
time in a week or two. Thanks.

On Sun, May 8, 2011 at 09:57, Martin Pool <email address hidden> wrote:
> @Adam this is probably pretty easy to fix; if you'd like to try we will
> help
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/172506
>
> Title:
>  allow users to force an empty commit message
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bzr/+bug/172506/+subscribe
>

Revision history for this message
Martin Pool (mbp) wrote :

Come and ask on #bzr or the mailing list if you want to talk about it.
 You don't need to write the fix alone.
Martin

Revision history for this message
Adam Porter (alphapapa) wrote :

What a great attitude! If only all FOSS projects were like this! :)

On Tue, May 10, 2011 at 05:53, Martin Pool <email address hidden> wrote:
> Come and ask on #bzr or the mailing list if you want to talk about it.
>  You don't need to write the fix alone.
> Martin
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/172506
>
> Title:
>  allow users to force an empty commit message
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bzr/+bug/172506/+subscribe
>

Revision history for this message
Stefan Wieser (swieser-n) wrote :

This bug should be closed, as it was fixed some time down the line, ie. Bazaar now does allow empty commit messages.

>bzr commit
Committing to: X
modified X.cpp
Commit message was not edited, use anyway? ([y]es, [n]o): no
bzr: ERROR: Empty commit message specified. Please specify a commit message with either --message or --file or leave a blank message with --message "".

>bzr commit -m ""
Committing to: X
modified X.cpp
Committed revision 2.

>

John A Meinel (jameinel)
Changed in bzr:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.