[bug 0.11] bzr ci -m allow no message to be specified

[Jari Aalto]

James Westby <jw+debian at jameswestby.net> writes:

> On (23/11/06 13:53), Jari Aalto wrote:
> > Aaron Bentley <aaron.bentley at utoronto.ca> writes:
> > > 
> > > It can happen under any release.  Your command there is "commit all
> > > files, with the message 'file.txt'", and I doubt that there's an
> > > automatic way to detect that this is not what you meant.
> > 
> > Oh, then make this alwasy require argument (like "."), so that this mistake
> > does not happen by accident:
> > 
> >     $ bzr ci -m file.txt      
> >     Syntax error, needs file or directory "." to commit all
> > 
> 
> I don't like this idea. I think that the other proposal of asking for
> confirmation if the message is the same as a file is a better one.

If this means interacitve questions, please don't. It will make bzr 
inpossible to be used in scripts and backends.

Jari