[PATCH] 306394 fix (warning, not error, on non-existent file)

[Karl Fogel]

John Arbash Meinel <john at arbash-meinel.com> writes:
>>> $ echo "public_branch = http://bazaar-vcs.org/bzr/bzr.dev" >>
>>>   bzr.dev-trunk/.bzr/branch/config
>> 
>> Done.  (I admit I'm not quite clear on why this is necessary; Googling
>> and trawling bazaar-vcs.org hasn't totally enlightened me yet.)
>
> This sets the "submit_branch:" in the bundle to something other than
> your local directory. Bundle buggy can use that to pull extra revisions
> that did not end up in the bundle.
>
> It still would have failed in this case, because the public location
> isn't actually an exact match for your local branch (because you merged
> rather than pulled.)

Hmmm.  But remember, I'm generating the bundle from over in
bzr.dev-306394 (which is a branch of bzr.dev-trunk, which is a branch of
http://bazaar-vcs.org/bzr/bzr.dev/).  

Does setting the public_branch in FOO really affect the submit_branch of
bundles created in a branch of FOO?

> Personally, I find that a checkout is good for my "bzr.dev" branch.
> Because that ensures that I can't commit to it. You can get there with:
>
> cd bzr.dev-trunk
> bzr bind http://bazaar-vcs.org/bzr/bzr.dev

Done.

> If you ever try to 'bzr commit' in that branch, it will tell you that it
> cannot lock an HTTP transport.
>
> At that point, you use "bzr update" to update your copy, which also
> (IMO) feels like a 'update my mirror' rather than merge or pull (though
> pull is also update-my-mirror, just for non-checkouts.)

Uh.  Right.

So.  Much.  To.  Learn.

:-)