[Fwd: Re: [BUG] apply_changeset / generate_changeset use wrong base]
John A Meinel
john at arbash-meinel.com
Wed Oct 5 15:46:58 BST 2005
Aaron Bentley wrote:
> John, any further thoughts on this? Do you agree with my summary?
>
> Aaron
>
...
>
> So, is this what we're saying?
> 1. Any changeset can be applied to a blank branch
I would say that a "null:" based changeset can be applied to a blank
branch, otherwise you wouldn't have the context. Remember the
destination branch has to have the changeset base so that it can
recreate the revision.
> 2. By default, unrelated changesets cannot be applied to a branch
Agreed.
> 3. If you specify a flag, you can apply an unrelated changeset to a branch.
Agreed. You still have to have the changeset base, or it won't know how
to unpack the changeset, but that can be unrelated to the actual changes
that exist. (You could always do a base of 'null:' which would mean the
current state would show up as all adds, and any branch could pull it
into its archive, but may not be able to apply it to the working tree,
without a flag).
John
=:->
>
> Aaron
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051005/40bdf640/attachment.pgp
More information about the bazaar
mailing list