[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Git migration and ECF 3.4 timing: PLEASE READ
- From: Wim Jongman <wim.jongman@xxxxxxxxx>
- Date: Tue, 3 Aug 2010 12:25:07 +0200
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=j1ZJb70Ft+dhfJnycgetb+f11OEECQ7kVraqnIXPFXMBG2kiSwcII745FIHJhmPMmF gq4CUHv/k6lue3w062milsatOPShSrqgsi4ieG9O7rOZr9eHV5zpr8+I8U43OgmXMKDc 13hP2jKgmEnw71IUFSY+eZwsSMVYcspB3/ngI=
d) So the bottom line, I believe, is that once we do the changeover that we should effectively plan on *shutting off CVS access* in favor of the git repo *only*. The reason we think this will be easier is because even if we try to sync the CVS repo with the git repo (i.e. 'b'), it will be a lot of work to do so frequently enough to make it worthwhile...as Eclipse IT won't do it for us, we won't be able to automate it, and we don't currently have the resource for us to do it manually with very high frequency
Do we need access to the CVS machine to run the cron job? Can't we fire a job on an intermediate machine that syncs cvs with git?