dry-run option for pull, merge, etc

[Martin Pool]

It would be nice to see what files will be updated by a pull/merge before doing it. This might help the user in seeing whether they want to pull or not.

We could possibly also show where conflicts will occur.

The common cvs idiom "cvs -n update" shows both local files and files which will be updated. svn status by default shows only locally modified files, but will show potentially-updated files if '-u' is given. Separating them is probably good.

[Aaron Bentley (abentley)]

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

Martin Pool wrote:
| Public bug reported:
|
| Affects: bzr (upstream)
| Severity: Wishlist
| Priority: Low
| Status: Unconfirmed
|
|
| Description:
| It would be nice to see what files will be updated by a pull/merge
| before doing it. This might help the user in seeing whether they want
| to pull or not.
|
| We could possibly also show where conflicts will occur.

This should be pretty easy. Instead of applying the transform, finalize it.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEMQxU0F+nu1YWqI0RAiNDAJwNRofhiCgL8Aj53ZSFouNvkN3L6wCfYLcy
UlzQ7TszJALENAzVQDyr0vQ=
=I9JK
-----END PGP SIGNATURE-----

[Martin Pool (mbp)]

Making it minor because it's quite a desirable feature.

[Joakim (joakim-cb)]

Bumpedibump :-)
dry-run option on all commands is highly desirable methinks.