[ECOS] Keeping 2.0 source tree up to date

[Roland Caßebohm]

On Dienstag, 23. September 2003 13:03, Reinhard JESSICH wrote:
> I would *not suggest* using the vendor branch feature of CVS directly on
> the main branch, as you might end up with an inconsistent state (at least
> temporarily).
>
> Here is what we are doing:
>
> We checked out a local copy from the annon CVS. Then we imported
> it to our CVS main branch with the "cvs import" command. After that we
> created a branch and started our own developments on this branch.
>
> We have a cron job running, which will update the local copy of the annon
> CVS weekly and generate a diff report about the ChangeLog files. This
> report is checked by the developers and if there is an interesting change,
> we import from the local copy of the annon CVS to our main branch "cvs
> import vendor-tag release-tag". We do this at least once in two months, to
> keep track of the ongoing development.

Is vendor-tag everytime the same, or do I have to rename it everytime I call
cvs import?
With release-tag I will do somthing like release-yyyy_mm_dd, but I'm not 
sure what to do with the vendor-tag.

Thank you,
Roland

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss