Transplant workflow question

[Hugues Lismonde]

Hi,

I'm playing with the transplant extension and it working very well but  
I'm wondering if my workflow is correct.

Here is the thing, I have a project (work in progress) which is cloned  
to be customized for each client.

Work is done on both the "main" project and the clones and I cherry  
pick the changes I want from the clones back into the main project  
(since some of the changes are specific to the client, this works very  
well).

Then, when I make some correction in the base project and I pull them  
into the clones. This also work well but the transplanted changesets  
are pulled alongside the new as another branch and merged. Until now  
it works but I feel it may not be as clean as it should.

I'd rather not transplant back and forth changes but if it's the  
safest way I'll follow it.

Is there another way to maintain client branches without pulling in  
the base repository changes/modules specific to those clients? While  
keeping the possibility to update them simply by push/pull between  
repositories?

If it's too confusing I'll gladly try to clarify what I'm trying to do.

Any help/advice would be greatly appreciated.

Thanks,
Hugues