>
> Thanks. I'm not so familiar with launchpad. So if I want to resubmit the
> proposal, should I push to a new branch?
No, that was already perfect. You do not need to push a new branch.
If you want to update your branch (with the whitespace fix I posted above, for example), simply make your changes locally, then "bzr commit" and then "bzr push" again. This will update this branch with your new commit.
Workflow is like this:
First propose a branch, then get a review with improvement suggestions, implement and commit those, push again to update the merge request, ...
>
> Thanks. I'm not so familiar with launchpad. So if I want to resubmit the
> proposal, should I push to a new branch?
No, that was already perfect. You do not need to push a new branch.
If you want to update your branch (with the whitespace fix I posted above, for example), simply make your changes locally, then "bzr commit" and then "bzr push" again. This will update this branch with your new commit.
See examples of this here: /code.launchpad .net/~mc- return/ compiz/ compiz. merge-thumbnail -improvements/ +merge/ 170548
https:/
Workflow is like this:
First propose a branch, then get a review with improvement suggestions, implement and commit those, push again to update the merge request, ...
(If you have additional questions, just ask)