Re: some bzrmerge.el questions

[Stefan Monnier <monnier@iro.umontreal.ca>]

> I realize I am confused by "skipping". Naively, I thought skipping
> would exclude the relevant revision entirely. However, a comment in
> bzrmerge-apply says that it still merges the meta-data. I guess this
> explains why revno: 99634.2.749 "!!!DO NOT MERGE TO THE TRUNK!!!" [1]
> now shows up in `bzr log -n0' output on the trunk, even though I said
> it should be skipped. Isn't it confusing to not merge the data, but
> still merge the meta-data?

There is simply no way in Bzr to merge part of a branch history: the
only kind of merge info recorded in the metadata says "all the branch
upto <foo> has been merged".

And really if you think about it, those "don't merge to trunk" changes
are usually changes which have already been performed on the trunk (tho
in a slightly different way, typically), so "applying" the corresponding
change amounts to doing nothing: if you used "bzr merge" instead of "M-x
bzrmerge", then you'd get spurious conflicts which you'd resolve by
choosing the pre-existing trunk version.  So bzrmerge just helps you
avoid those conflicts.


        Stefan