Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: release management
- X-seq: zsh-workers 8583
- From: Adam Spiers <adam@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh workers mailing list <zsh-workers@xxxxxxxxxxxxxx>
- Subject: Re: release management
- Date: Sat, 6 Nov 1999 11:35:20 +0000
- In-reply-to: <19991105163945.A1971@xxxxxxxxxxxxxxxx>
- Mail-followup-to: zsh workers mailing list <zsh-workers@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <19991027104033.A29314@xxxxxxxx> <19991027165016.A79545@xxxxxxxxxxxxxxxxxxxxxxx> <19991102165034.A12065@xxxxxxxxxxxxxxxxxxxxxxx> <991103082052.ZM3082@xxxxxxxxxxxxxxxxxxxxxxx> <19991104203338.C12554@xxxxxxxxxxxxxxxxxxxxxxx> <19991104144755.A802@xxxxxxxxxxxxxxxx> <rsq3dulvftm.fsf@xxxxxxxxxxxxxxxxx> <19991105162837.A23680@xxxxxxxxxxxxxxxxxxxxxxx> <19991105152100.A31482@xxxxxxxx> <19991105163945.A1971@xxxxxxxxxxxxxxxx>
- Reply-to: Adam Spiers <adam@xxxxxxxxxx>
Dan Nelson (dnelson@xxxxxxxxxxxx) wrote:
> You can sort-of do this by having the "CVSROOT/loginfo" action send an
> email to everyone running CVS mirrors (possibly using a list alias) on
> commits. Each mirror site would have a procmail script that triggers
> off the subject and runs "cvsup -s zsh-supfile". That line takes about
> 15 seconds to run assuming no changes have been made, so it shouldn't
> tax the network.
Yep, something like this would be nice. There's a slight problem in
that commits tend in practice (I find) to be done in bursts, so you
might be sending more than one `do a cvsup -s now' instruction to the
mirrors within a small time span. However I get the impress that
cvsup is so efficient this would be no great disaster anyway.
P.S. Tanaka, if you decide to do this loginfo trick, could you include
zsh-mirror@xxxxxxxxxxxxxxxxxxxxxxx on the list of e-mail addresses to
notify?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author