about bzr status --short

[Alexander Belchenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Today I try to use 'bzr status --short'. Very nice.

But I have some questions.

1) Can we provide short name for option --short? May be -s?

2) Status of working tree after merge with conflicts:

 M  NEWS
 M  bzrlib/osutils.py
 M  bzrlib/urlutils.py
 M  bzrlib/tests/test_osutils.py
 M  bzrlib/tests/test_urlutils.py
?   NEWS.BASE
?   NEWS.OTHER
?   NEWS.THIS
C   Text conflict in NEWS
P   Alexander Belchenko 2007-02-14 NEWS entry
P.   Alexander Belchenko 2007-02-14 win98_abspath:
P.   Alexander Belchenko 2007-02-14 Don't do normpath
P.   Alexander Belchenko 2007-02-14 Reimplementation

^-- Why we print 'C' on separate line? Only because we want to
print 'Text conflicts in...'? It could make machine parsing
is slightly harder, is not?
Also note that 'P.' is not documented in help.
I don't know is dot really needed?
I think for machine parsing of this output it will be OK.
When we do octopus merge there will be several heads with
'P' and then their parents, is it?
Just tiny little note.

Alexander


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF0uzdzYr338mxwCURAuDiAJ9ix6u9Du5/YQQdoAexzGLTJgnIKQCbBaEp
VCln+OLjXMEbb9mmfiWQrVA=
=4PNW
-----END PGP SIGNATURE-----