> Sorry, that sounds a bit harsh. I meant to say I can /no longer/
> reproduce this bug with current versions of bzr-svn/bzr. I was able to
> reproduce at least one of the two ghost issues you reported earlier.
Does this mean that current versions of bzr-svn/bzr can deal with ghost revisions or they don't create them any more? If it means that they don't create them any more but still can't deal with them being present is there any way of fixing existing repositories that contain ghost revisions?
Also, by "current versions" do you mean "current in-development versions" or "current releases i.e. bzr 2.2.1 / bzr-svn 1.0.4"?
On 1 Oct 2010, at 09:58, Jelmer Vernooij wrote:
> Sorry, that sounds a bit harsh. I meant to say I can /no longer/
> reproduce this bug with current versions of bzr-svn/bzr. I was able to
> reproduce at least one of the two ghost issues you reported earlier.
Does this mean that current versions of bzr-svn/bzr can deal with ghost revisions or they don't create them any more? If it means that they don't create them any more but still can't deal with them being present is there any way of fixing existing repositories that contain ghost revisions?
Also, by "current versions" do you mean "current in-development versions" or "current releases i.e. bzr 2.2.1 / bzr-svn 1.0.4"?
Thanks,
Francis