Hi Robert, 

Oh, I see that I wasn't quite clear: I meant *you* to check and merge
the changes, not *me*. I didn't intend to mess with files, which I don't
understand and I don't have to modify. 

I see that you actually cloned the care2x project to this
elc_tanzania-0-2 in order to make an east african solution and you are
interested to work in this branch. 
It is in my interested to get the g2_deployment_2_1 branch in a working
state, so if you don't have enough time (which is probably the case) I
can try to do something about this. 
Unfortunately, it is not only the case that almost nobody is using the
cvs in this project, but the few people, who do it, do not used to write
meaningful log messages in their commits. It will be very hard to me to
understand the meaning of the changes during the last 9 months. So,
every comment from your side about which changes in elc_tanzania-0-2 are
appropriate for merging with g2_deployment_2_1 will be very useful. 

I have not much experience with cvs. I have > 3 years professional
experience with Perforce, though. It is quite different and now I read
the "Open Source Development with CVS" book. I recommend it to everyone!
It can be freely downloaded from this site: 

http://cvsbook.red-bean.com

I am going to read the entire book and hopefully will get more knowledge
about the branch/tag/merge/diff/patch-ing capabilities of cvs. Then I
will make a summary of the differences between the elc_tanzania-0-2 and
g2_deployment_2_1 branches and will try to make something. 

Greetings
Kaloyan


On Sat, 2005-09-10 at 15:07 +0200, Robert Meggle wrote:
> Hello Kaloyan,
> 
> > Robert, I see that it is you who made this commit in the CVS. Is it
> > possible to check your commits in the elc_tanzania-0-2 branch and merge
> > the appropriate changes to the g2_deployment_2_1 branch?
> 
> Yes and no, could be done, but do it later! Be careful at the moment! We
> made some specific solutions for the east african requirements and if you
> merge the whole development tree, the specific solutions would be merged as
> well.
> We´re making later a release that has full compatibility to the main
> development stream, there are some preperations done for realizing it. But
> acutally our devleopment is very specivic and we have to test it. Also we
> create some new modules and changed e.g. the laboratory and the pharmacy
> module nearly completely.
> 
> So if you´re doing it, do it not for all folders. For our branch we had
> added all missed files especially for the adodb-folder. In these days, when
> I found the troubles with missed files, I expected a misuse for my
> cvs-frontend and didn´t had any idea that these files in deed missed on the
> cvs server as well. Because: I made this cvs-download at january last time
> and there was no one here that reported of this issue. Unbelevable that
> nobody here using cvs.
> 
> Fact is, all fundamental files are available in the zip file of care2x in
> the download section, but not in the cvs. Maybe it is possible for you to
> make the "2G Deployment 2.1 FULL PACK + PATCHES D-2.1.0.1" to a working
> release? Would be great!
> 
> 
> Robert
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Care2002-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/care2002-developers



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Care2002-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/care2002-developers

Reply via email to