Comment 4 for bug 615729

On Tue, 2010-08-10 at 07:13 +0000, Jeroen T. Vermeulen wrote:
> Public bug reported:
>
> Sometimes with bzr (and other revision control systems) I have little
> accidents:
>
> $ bzr commit -m src/foo.c -m "Dobnialicate the shingle."
> modified:
> doc/README.txt
> include/bar.h
> src/foo.c
>
> Argh! I committed stuff I didn't mean to, and probably with a
> nonsensical message.
>
> The fault is mine, and it'd be hard (though probably not impossible) to
> catch all mistakes of this type. Still, wouldn't it make more sense to
> error out when -m is specified more than once on one command line?
FWIW Subversion disallows commits that have a commit message that
matches an existing file path, and it really annoys me.

("svn add foo; svn ci -m foo")

Detecting duplicate -m arguments seems reasonable, though.

Cheers,

Jelmer