[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] gzigzag commit policy?
- To: zzdev@xxxxxxxxxx
- Subject: Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] Re: [zzdev] gzigzag commit policy?
- From: Antti-Juhani Kaijanaho <gaia@xxxxxx>
- Date: Tue, 4 Jul 2000 12:23:19 +0300
- In-reply-to: <Pine.LNX.3.96.1000704050433.24020Q-100000@fuga>; from lukka@xxxxxx on Tue, Jul 04, 2000 at 05:05:53AM +0300
- Mail-followup-to: zzdev@xxxxxxxxxx
- References: <20000704115109.D16685@xxxxxxxxxxx> <Pine.LNX.3.96.1000704050433.24020Q-100000@fuga>
- Sender: Antti-Juhani Kaijanaho <ajk@xxxxxxxxxxx>
On Tue, Jul 04, 2000 at 05:05:53AM +0300, Tuomas J. Lukka wrote:
> Or do you have a simple solution (that doesn't take long after the update?)
No, although it would be possible to set up a cronjob to put up a
changelog in a known place and update it, say, every five or fifteen
minutes. Could also put in some postcommit magic to make sure it does
not rebuild the changelog when no commits have happened.
--
%%% Antti-Juhani Kaijanaho % gaia@xxxxxx % http://www.iki.fi/gaia/ %%%