[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] gzigzag commit policy?
- To: Antti-Juhani Kaijanaho <gaia@xxxxxx>
- Subject: Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] gzigzag commit policy?
- From: "Tuomas J. Lukka" <lukka@xxxxxx>
- Date: Tue, 4 Jul 2000 14:54:59 +0300 (EEST)
- Cc: zzdev@xxxxxxxxxx
- In-reply-to: <20000704130038.C16943@xxxxxxxxxxx>
> So, we have at least three possible ways of doing this: a commit hook
> using cvs2cl (rebuild it at every commit; but this is wasteful, since the
> cvs2cl does not do incremental builds);
Actually, it does allow "since day X", doesn't it?
> a commit hook using a homebrewn
> incremental script;
Possible. Possibly based on cvs2cl
> a cronjob doing cvs2cl builds at regular intervals
> and committing the ChangeLog if it changes.
Not nice: it should remain up to date as much as possible. But this could
be a good start (probably the simplest to set up?).
Tuomas