oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

I see Eduardo is very busy today.  :-)

I would like to point out that *if* the decision is made to merge the
mlhim branch then each commit that is made to the trunk will increase
the manual work needed when the merge is executed. 

So a decision should be made as soon as possible.  

If the decision is to *not* merge the mlhim branch; I would really like
to know why not.

This is an important and urgent issue.

Thanks,
Tim 

On Thu, 2010-08-05 at 22:02 -0500, Tim Cook wrote:
> On Thu, 2010-08-05 at 21:32 -0500, Tim Cook wrote:
> 
> > 
> > I have restructured your repackaging and created a new branch. It runs
> > fine. I suggest that you merge it with the development branch.
> > 
> > https://code.launchpad.net/~oship-dev/oship/repkg/+merge/31921
> 
> Please note that if you merge the mlhim branch 
> https://code.launchpad.net/~oship-dev/oship/mlhim/+merge/31923
> 
> then you  do not have to merge the repkg branch.
> 
> --Tim
> 

-- 
***************************************************************
Timothy Cook, MSc
Project Lead - Multi-Level Healthcare Information Modeling
http://www.mlhim.org 

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or    
from this link http://timothywayne.cook.googlepages.com/home

Attachment: signature.asc
Description: This is a digitally signed message part