reconfigure --tree should set pull location

Bug #387034 reported by Neil Martinsen-Burrell on 2009-06-14
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Wishlist
Unassigned

Bug Description

Use case: I want to have a local mirror of lp:bzr-keywords which I originally make with ``bzr co lp:bzr-keywords``. This may be Subversion habits persisting in starting with a checkout command. Later, while updating my plugins with ``bzr pull``, I find that there is no pull location (I should have used ``bzr up`` in the checkout). I discover that I took a checkout rather than a branch using ``bzr info`` and so I know that I want to make my checkout into an unbound branch. So I look at the help for reconfigure and I do ``bzr reconfigure --tre`` (which works even with the typo), but now I've lost all knowledge of the original location that my branch was bound to.

Expected Behavior: I expected that the bound location would be preserved somewhere in the unbound branch, in this case I would have wanted it set as the default pull location. I suggest that reconfigure --tree should set the pull and push locations to the bound location.

Robert Collins (lifeless) wrote :

Sounds like you want 'reconfigure --tree' to behave identically to 'bzr unbind' in this case. Seems reasonable and its a bit odd that it didn't.

Changed in bzr:
importance: Undecided → Wishlist
status: New → Confirmed
Jelmer Vernooij (jelmer) on 2011-11-21
tags: added: reconfigure
Jelmer Vernooij (jelmer) on 2017-11-09
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers