Andrew Voznytsa wrote:
> I was under impression that rm --new remove non-versined files from 'add
> queue' whereas rm --keep/--force work with already versined files.
No, --new is an alternative to specifying particular files.
> I guess it would be better to drop '--new' at all
It does serve a useful purpose, so I'm not sure that makes sense.
> adjust documentation
> to clearly state that rm --keep/--force works for unversioned-but-
> queued-for-versioning files too.
We actually consider those files to be versioned, not
unversioned-but-queued.
>>From my experience bzr 0.14 did not require anything besides --new to
> remove just added file from 'add queue'.
bzr 0.14 did not require --new if you specified filenames.
To get the old behavior, use --keep.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrew Voznytsa wrote:
> I was under impression that rm --new remove non-versined files from 'add
> queue' whereas rm --keep/--force work with already versined files.
No, --new is an alternative to specifying particular files.
> I guess it would be better to drop '--new' at all
It does serve a useful purpose, so I'm not sure that makes sense.
> adjust documentation for-versioning files too.
> to clearly state that rm --keep/--force works for unversioned-but-
> queued-
We actually consider those files to be versioned, not but-queued.
unversioned-
>>From my experience bzr 0.14 did not require anything besides --new to
> remove just added file from 'add queue'.
bzr 0.14 did not require --new if you specified filenames.
To get the old behavior, use --keep.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFGZHsM0F+ nu1YWqI0RAuM7AJ 0a7M5hkxWaib2lp VYH5TnMIUiQBACc C1+y p2rJxXPI=
LZoJrPAFOyJsY86
=CWx1
-----END PGP SIGNATURE-----