bobby temper wrote:
Hello CVS users,
The company i work for is having difficulties keeping production and
the repository in sync'.
Not sure what you mean by production and repository in sync ? Did you
mean to say you want to have two repositories that need to be kept in
sync ?
If yes you may want to look at http://www.wandisco.com/cvs for keeping
multiple replicas in sync.
I would like to know, what is the best practice to achieve this? I'm
thinking of having a cvs client on production, and having the
production code being a checked out copy, with a cron job doing a cvs
-n update, and emailing the results. But I am not sure thats the best
way, as
Looks like you want to determine what changed against a poduction
tag/branch ? If yes
you might want to create a tag and diff against that.
other problems might occur with this solution. I would like to know
if any of you have a better solution, or see the pitfalls in such
solution.
Thanks for your help,
Best regards,
Bobby
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's
FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/info-cvs