Bazaar

  1. Bug #45719
  2. Comment #40

Comment 40 for bug 45719

Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 45719] Re: update command cannot take a revision number

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

Julien wrote:
>>> If I simply want to inspect
>>> previous versions, I wouldn't want "bzr status -V" to list all the files
>>> changed between the older revision and the current one.
>> Why is that a problem?
>>
> If I actually want to do a revert, I can see that this makes sense.
> For update however, I wouldn't want the list of files that I edited to
> be overwhelmed by the list of changes between the two revisions.

All I'm saying is that revert is an option for the use cases you listed:

* try and track down which change introduced a bug
* compare the performance of different versions on specific testcases
* inspect earlier versions of the code base, for whatever reason

It's a bit surprising to me that you would also want to retain
uncommitted changes and examine them while doing those things, but if
you do, I agree that revert is not suitable.

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

iEYEARECAAYFAktwfdoACgkQ0F+nu1YWqI2iWACeKNRbcmnsOvXuCQU4nDMZ1Qtl
7y0An2qDTEu3cGTb9JZpZmdLa01TgJBJ
=H4ZY
-----END PGP SIGNATURE-----