Everything is in the title ...
$ bzr push Using saved location: /path/to/push/location [ bzr actually pushes ] No revisions pushed. $
how many revisions were you expecting to be pushed ?
Forget this bug, I don't remember exactly how to reproduce it, and it seems to have been fixed in the meantime anyway (I'm the original reporter).
Oh, strange coincidence : I've just hit the bug again ;-).
This happens when push creates a branch:
(with nothing in /tmp originally)
cd /tmp bzr init bzr-branch cd bzr-branch touch foo bzr add bzr commit -m foo touch bar bzr add bzr commit -m bar bzr push /tmp/bzr-branch-pushed
I don't suppose you could write a blackbox test for this ?
Given my time now and my skills in python, not before 2 weeks from now, ...
confirmed this, it occurs on the first push.
This has been fixed at least in bzr.dev, but still exists in bzr-0.8.2
Why is this not targeted for a 0.8 point release? Or are there going to be no more?
This is not a security or performance bugfix, so it is not a specific candidate for backporting. But it will be released in 0.9
Bug watches keep track of this bug in other bug trackers.
how many revisions were you expecting to be pushed ?