[Pkg-bazaar-maint] Use of 'bzr merge-upstream' in bzr-explorer

[Max Bowsher]

Hi,

I've just had the occasion to import a new upstream version into the
bzr-explorer packaging branch, in preparation for PPAizing it.

I have done so using 'bzr merge-upstream', as I believe that's what
we're using for everything now?

I'm sending this email because the bzr-explorer branch had not had 'bzr
merge-upstream' used on it before, and I want to make sure everyone is
aware of it, and that I am not confused about this being the correct
approach now.

The primary usefulness of using 'bzr merge-upstream', as I see it, is
automatic stashing of pristine-tar metadata in the bzr revision, such
that future use of 'bzr builddeb' will be able to produce a package from
the branch alone.


Max.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-bazaar-maint/attachments/20101202/bfb6df62/attachment.pgp>