Re: concurrent development, two repositories

[Pierre Asselin]

Arthur Barrett <address@hidden> wrote:
> [-- text/plain, encoding quoted-printable, charset: us-ascii, 44 lines --]

> Jeffery,
>  
> I just recently also came across a scenario where this was required.
>  
> As Pierre pointed out the best alternative is to use vendor branches
> instead and have the other developers send a complete tarball.

Now that I think of it, you could live with patches.

    cvs checkout -ko -rVENDOR the_project
    cd the_project
    patch -p1 < ../the_latest_patch
    cvs import -m'patch, date' the_project VENDOR new_release_tag

The import command will ignore the CVS/ subdirectories and the net
result will be as if you were importing a tarball.  It's a little
error-prone, on your side and theirs, so be careful.


-- 
pa at panix dot com