[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Storing static code

From: bollu
Subject: Re: Storing static code
Date: Thu, 30 Jan 2003 12:12:32 +0100

>WE have an existing cvs setup where we would like to hold the original
>code that the vendor has sent out - before we mod'd it - so we can do
>diffs against the original code (assume we originally imported code that
>had already been mod'd) to find out what has changed.
>Our thinking goes something like this.
>1. Create a branch.
>2. Checkout and remove contents of that branch
>- we then have an empty directory on our local copy
>3. Copy the original vendor code in
>4. cvs add and commit it
>This would, in theory, leave us with a copy of the vendor code in a branch
>of it's own.

What about just importing the vendor code under another vendor branch?

  cvs import repository vendor_tag2 release_tag

This way, you would have 2 vendor branches; One with the original
unmod'd vendor code and another one with your mod'd code.

Something like this:

      |             |                       |
    TRUNK  mod'd vendor branch   unmod'd vendor branch
      |             |                       |
      |          release_1             release_1

>How does this sound ?

How does it sound?

>One last question - once we've done this can we make it read-only in CVS
>(without making it r/o at the o/s level) ?

don't think so.



This mail, and any attachments thereto, is intended only for use by the
addressee(s) named herein and may contain legally privileged and/or
confidential information.
If you are not the intended recipient, please note that any review,
dissemination, disclosure, alteration, printing, copying or transmission of
this mail and/or any file transmitted with it, is strictly prohibited and
may be unlawful.
If you have received this mail by mistake, please immediately notify the
sender as well as our mail administrator at address@hidden, and
permanently destroy the original as well as any copy therof.(Embedded image
moved to file: pic12287.pcx)

Attachment: pic12287.pcx
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]