4 messages in com.perforce.perforce-user3rd party lib src
FromSent OnAttachments
Robe...@SCRAP.de30 Sep 1997 05:51 
Paul...@geoworks.com01 Oct 1997 00:04 
Brad...@email.mot.comBrad_Appleton-GBDA00101 Oct 1997 00:10 
Robe...@SCRAP.de01 Oct 1997 01:00 
Subject:3rd party lib src
From:Robe...@SCRAP.de (Robe@SCRAP.de)
Date:09/30/1997 05:51:21 AM
List:com.perforce.perforce-user

-----Original Message----- From: Tom Bjorkholm <Tom.Bjorkholm at ebc.ericsson.se> To: r.m.muench at ieee.org <r.m.muench at ieee.org> Date: Dienstag, 30. September 1997 09:55 Subject: 3rd party lib src

why not check in the 3rd party library source as it is. Then create a branch where you are making all your changes.

Ok, this would be a way.

When you get a new version you check it in on the main branch. Then integrate/merge the changes between the version to your branch.

The merging not always makes sense. And how do I get all the file stuff solved (it's easy to add new files but to find out which files have been removed (maybe even renamed) is a lot harder)

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?