Comment 3 for bug 50793

'bzr diff' 'bzr add' and 'bzr status' have been fixed.
But 'bzr log' still acts like no file was given, and 'bzr commit' just gives:
bzr: ERROR: no changes to commit. use --unchanged to commit anyhow

Now, you get a real error if you don't supply a message:
liliana % bzr commit "a commit log which actually seems to be a file"
bzr: ERROR: Path(s) do not exist: "a commit log which actually seems to be a file"

So it seems we need more explicit handling of it for 'bzr commit'.