How to chnage the URL after a branch location change

Russel Winder russel.winder at concertant.com
Tue Oct 6 15:38:06 BST 2009


On Tue, 2009-10-06 at 10:34 -0400, John Yates wrote:
> Jonathan Lange wrote:
> 
> > >    bzr init-repo --trees project
> > >    cd project
> > >    bzr branch <URL> upstream
> > >    bzr branch upstream local
> > >    ... work
> > >    ... then one day the original <URL> moves to another location
> > >
> > > How do I make the 'upstream' to point to a new <URL> location for pull 
> > > operations?
> > 
> > cd upstream
> > bzr pull --remember <NEW_URL>
> 
> Interesting that recording a <NEW_URL> is exposed as a side effect of pull.  What if I receive notification of a changed URL and want to act on that information before it slips my mind but am not ready to perform a pull?  Am I reduced to piercing the abstraction and editing .bzr/branch/branch.conf directly?
> 
> How will Explorer handle this use scenario?

You could use bookmarks.  Although the default is to store all bookmarks
globally I use a lot of branch-specific bookmarks.

	bzr help bookmark
	bzr help bookmarks

-- 
Russel.
=============================================================================
Dr Russel Winder      Partner
                                            xmpp: russel at russel.org.uk
Concertant LLP        t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,   f: +44 8700 516 084   voip: sip:russel.winder at ekiga.net
London SW11 1EN, UK   m: +44 7770 465 077   skype: russel_winder
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20091006/484c1196/attachment-0001.pgp 


More information about the bazaar mailing list