Making a branch tree-less
russel.winder at concertant.com
Mon Oct 13 10:39:14 BST 2008
On Mon, 2008-10-13 at 09:09 +0100, Daniel Watkins wrote:
> Hi Russel,
> On Mon, 2008-10-13 at 08:30 +0100, Russel Winder wrote:
> > I am in a situation where I have a central mainline branch accessible by
> > people using SSH. When I push up to this branch, I am getting:
> > This transport does not update the working tree of: bzr
> > +ssh://XXXXXXXXXXXXX. See 'bzr help working-trees' for more information.
> > No new revisions to push.
> > As far as I can tell the central branch in question has no working tree
> > and indeed never has. So my question is what do I have to do to the
> > central branch to avoid getting this, for me in this situation, spurious
> > warning.
> 'bzr remove-tree'.
Hummm.... this is what I had done a long time ago, so didn't think to
just try it again. I just have and the message has stopped. Whether
there is a causal relation who knows :-)
Thanks for pushing me to try the obvious. I am now in a good state :-)
Dr Russel Winder Partner
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084
London SW11 1EN, UK. m: +44 7770 465 077
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20081013/2f9b414e/attachment.pgp
More information about the bazaar