Code review comment for lp:~motuscience/ubuntu/karmic/k3dsurf/version0.6.2.4

Sure - I've been working with gnome-power-manager which used to have a
very different way maintaining that package (we keep only the debian
file in ~gnome-power-manager-team's bzr branch), so I actually just
kept the debian directory and replaced the rest. Here's my reasoning
and steps:

1) For this package I just compared our bzr branch to the upstream
source, saw that the only difference was the debian directory, so I
deleted everything except for debian/ then extracted the upstream
source into the folder. (This is so all the bzr functionality was
maintained).
2) ran "bzr add -a" which just logged that the Makefile was moved
3) "dch -i" for the new version
4) "bzr bd --builder pbuilder" (tested that it built, installed, ran)
5) "debcommit"
6) bzr push

I've read on the mailing list that Ubuntu wants to go to bzr merges
instead of debdiffs, should I be doing bzr merges like this? Have you
found any interesting/better ways?

I'm applying for contributing developer:
https://wiki.ubuntu.com/ScottHoward/ContributingDeveloperApplication
If you have the time, could you put a testimonial for this package? Thanks!