dry-run option for pull, merge, etc
Bug #37829 reported by
Martin Pool
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Low
|
Unassigned | ||
| Breezy |
Triaged
|
Low
|
Unassigned | ||
Bug 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.
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.
Revision history for this message
| Aaron Bentley (abentley) wrote Re: [Bug 37829] dry-run option for pull, merge, etc | #1 |
Revision history for this message
| Martin Pool (mbp) wrote | #2 |
| Changed in bzr: | |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Joakim (joakim-cb) wrote | #3 |
| tags: | added: merge pull push |
| tags: | added: dry-run |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
-----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://
iD8DBQFEMQxU0F+
UlzQ7TszJALENAz
=I9JK
-----END PGP SIGNATURE-----