[RFC] Separating last-revision from parents

[Aaron Bentley]

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

Aaron Bentley wrote:
> Robert Collins wrote:
> 
>>>The current behaviour of update and revert is in my mind 'correct' -
>>>that is, we can probably improve it, buts its doing what I intended.
>>>
>>>I wanted the following to hold true for any tree:
>>> 'bzr update && bzr revert && bzr info -> no missing revisions, no local
>>>edits, no new local commits. 

> I'm not sure why you want bzr update && revert to throw away local
> commits.  Perhaps you could elaborate on that.  But it sounds like
> perhaps it could be achieved more conveniently with a flag to update,
> anyhow.

Ping?

Also, see Erik Bågfors' suggestion for merge --reverse, which I believe
would also work much better with a separation of last-revision and parents.

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

iD8DBQFF0fve0F+nu1YWqI0RArHAAJ0cwdS36yuZCa+1LvscdBKmPWM2yACffgQ8
PviYGcUpcMeBHk5ajF+3lmM=
=DmLT
-----END PGP SIGNATURE-----