[RFC] An explicit "this branch has moved" format

John Arbash Meinel john at arbash-meinel.com
Wed May 14 20:07:19 BST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matt Nordhoff wrote:
| John Arbash Meinel wrote:
|> Right now, Bazaar lets you use an HTTP redirect or a lightweight
|> checkout to
|> redirect people to a different location. I've used the lightweight checkout
|> trick a few times when I move something on my local system to being
|> officially
|> hosted on launchpad.
|>

...

|> Thoughts?
|>
|> John
|> =:->
|
| Don't forget that it needs to be able to specify it for either
| public_branch/push_location/etc. or http/bzr+ssh/etc.
|
| E.g.:
|
| $ bzr set-control --redirect public_branch http://bzr.foo.com/branch/
| $ bzr set-control --redirect push_location
| bzr+ssh://bzr.foo.com/srv/bzr/branch/ # and what about the username?
|
| If you can only set the redirect to one location, you'll have to break
| either users who pull or users who push.

For my particular use case, I only care about users that pull. But honestly just
getting a "bzr: ERROR this branch has moved" would also be sufficient. It means
things don't just auto-redirect, but at least it tells the user that they are
working in the wrong place. (I ran into this because of plugins that I moved to
be officially hosted on Launchpad, rather than on my own site. And then people
keep telling me that I 'broke' the plugin in the last commit.)

In some ways I would prefer something very simple, to

a) get it actually implemented and accepted, and
b) prevent feature creep from having a simple concept sprout 20-different ways
of configuring it.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgrOGcACgkQJdeBCYSNAAMN8gCgxGHVR/fXTb/exMmr8EB143Ra
aNgAoIZnddaSGnxY7bjmKr5yleOHtbY5
=jLj8
-----END PGP SIGNATURE-----



More information about the bazaar mailing list