John A Meinel wrote:
>>> flag at all, and is just pushing up the whole history.
>> It is reflecting the stacked flag some:
>> $ bzr branch . :push
>> Using default stacking branch /~launchpad-pqm/launchpad/db-devel at
>> bzr+ssh://bazaar.launchpad.net/%7Eabentley/launchpad/
>> Created new stacked branch referring to /~launchpad-pqm/launchpad/db-devel.
> Sure. It could, for example, set the 'stacked-on-url' in the Branch
> config, but not actually set a fallback repository on its Repository
> object. I'm certainly just guessing, but I think it is a reasonable
> guess of where to start looking.
AFAICT, it affects clone_on_transport also, but only if revision_id is
None. (Perhaps push forces the revision_id higher up the chain and
branch does not.)
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John A Meinel wrote: pqm/launchpad/ db-devel at //bazaar. launchpad. net/%7Eabentley /launchpad/ pqm/launchpad/ db-devel.
>>> flag at all, and is just pushing up the whole history.
>> It is reflecting the stacked flag some:
>> $ bzr branch . :push
>> Using default stacking branch /~launchpad-
>> bzr+ssh:
>> Created new stacked branch referring to /~launchpad-
> Sure. It could, for example, set the 'stacked-on-url' in the Branch
> config, but not actually set a fallback repository on its Repository
> object. I'm certainly just guessing, but I think it is a reasonable
> guess of where to start looking.
AFAICT, it affects clone_on_transport also, but only if revision_id is
None. (Perhaps push forces the revision_id higher up the chain and
branch does not.)
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkp VeoUACgkQ0F+ nu1YWqI0PNgCfSu S5F2UUhPpZoeDv3 5LSG9ZB 8Rfpbc3Jsl+ QUCpzp
epUAn2Uim31XxqG
=ErVf
-----END PGP SIGNATURE-----