3rd party lib src

RobertM.MuenchRobert.M.Muench at SCRAP.de RobertM.MuenchRobert.M.Muench at SCRAP.de
Wed Oct 1 01:01:13 PDT 1997


 -----Original Message-----
From: Brad_Appleton-GBDA001 at email.mot.com
<Brad_Appleton-GBDA001 at email.mot.com>
To: perforce-user at perforce.com <perforce-user at perforce.com>
Date: Mittwoch, 1. Oktober 1997 09:18
Subject: Re: 3rd party lib src

>This one came up on the clearcase list not too long ago.  One thing that
>folks seem to typically do for maintaining 3rtd party code is to keep
>two sets of branches.

Aha..

 >All the 3rdparty releases go on the "main" line of
>development, and all your local changes go on some kind of "customizations"
>branch and have to merge in the lastest stuff from the main-line when a
>new release is received.

I tried to avoid branching but maybe I should get used to it... I will give
it a try with the other stuff you send to me.

 >If you'll forgive my pitiful attempt at drawing
>version trees in ascii, the result is something like:

Hey, it looks good!

> ... some cool drawings deleted ...

Ok, I will try this solution and find out if I/we can handle it this way.
Thanks again.

Robert M. Muench
SCRAP EDV-Anlagen GmbH, Karlsruhe, Germany

==> Private e-mail: r.m.muench at ieee.org <==
       ==> ask for PGP public-key <==

    When do you want to reboot today?








More information about the perforce-user mailing list