Re: CVS migration to Mercurial

Francesco Romani wrote:

> Ooops, forgot to add two things.
> 
> The last thing I do really miss after the migration is the cvs-commit
> ML. It saved me a few headaches and potential problems because I read
> mail before to fire up coding (that prevented conflicts).
> 
> It is feasible to restore it?
> No big deal if no, just wondering :)

You should have received two test mails which were sent by the freshly 
configured "notify" extension. I used a test repository for that 
purpose, but it should work with the two transcode repositories as well.

Currently each incoming changeset will trigger a separate mail (as with
the cvs hook before). I can configure it on a per push basis if you 
like, just tell me.

Regards,

Jörn

P.S.: Mercurial is really good stuff. Everything's straight forward, no
"strange" things happens - it just works!

-- 
sub i($){print$_[0]}*j=*ENV;sub w($){sleep$_[0]}sub _($){i"$p:$c> ",w+01
,$_=$_[0],tr;i-za-h,;a-hi-z ;,i$_,w+01,i"\n"}$|=1;$f='HO';($c=$j{PWD})=~
s+$j{$f."ME"}+~+;$p.="$j{USER}\@".`hostname`;chop$p;_"kl",$c='~',_"zu,".
"-zn,*",_"#,epg,lw,gwc,mfmkcbm,cvsvwev,uiqt,kwvbmvb?",i"$p:$c> ";w+1<<07

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABEDAAYFAkl/dSIACgkQ2hNi0Chc9HPOkQCfWsuIrDddYdkubiriL2oUwEey
qbsAoLC5zvmEe+M6UrYjPxCyWU+dxzpP
=STl7
-----END PGP SIGNATURE-----