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?
>
> ** Affects: bzr
> Importance: Undecided
> Status: New
>
You can always "bzr uncommit" right after...
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
>
> ** Affects: bzr
> Importance: Undecided
> Status: New
>
You can always "bzr uncommit" right after...
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
g/osACgkQJdeBCY SNAAPlqwCfe+ s+MFyNXUf2EazQi WyzxIdD 22JhULbLDblRlks wb
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkx
sPUAoIfOSkEzTWs
=iDES
-----END PGP SIGNATURE-----