"bzr update -r REVNO" wanted
hack at robf.de
Sun Jun 25 15:01:51 BST 2006
On Friday, June 23, 2006 at 17:12:33, Aaron Bentley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Robert Widhopf-Fenk wrote:
> > How to do bisect to find the rev introducing a bug?
> > With Subversion I do "svn update -r REVNO" on a tree
> > without modifications, i.e. I "update" it to an older
> > version, sometimes I even do it with individual files.
> Do you need 'update' per se?
I was not aware of "revert -r REVNO" and I can
accomplish what I though doing with "update -r",
i.e. find which revision introduced a bug.
> 'revert -r' will update the tree contents, but 'status'
> and 'diff' will indicate changes relative to the last
> revision, not to the revision you reverted to.
But, it is kind of different from what I want as it will
revert all those changes in my local tree where "update -r"
will give me a clean tree where I can do a bugfix,
branch/shelve it and merge/update to head and unshelve it.
What exactly is the use case for "revert -r"?
For a moment I thought I could do a "revert -ra..b" to
revert all changes from the revisions a to b, but it seems
that it is only possible to revert changes from REVNO..HEAD.
To revert a..b I probably have to do
bzr diff -ra..b | patch -R
which does not handle renames.
Nevertheless, it would be nice to have a bzr command to
revert some older revisions not starting at head.
> > I would love to have "bzr update -r REVNO".
> Yes, it's been noted as a missing feature.
More information about the bazaar