Re: [Savannah-hackers] Re: Fwd: Sending m4 cvs commit notification to m4-commit list

[Loic Dachary]

 > S-> checkout (/cvs/m4/ChangeLog,v, 1.54, , (function))
 >  -> ParseInfo(/cvs/CVSROOT/commitinfo, m4, ALL)
 > S-> checkout (/cvs/m4/examples/include.m4,v, 1.1.1.2, , (function))
 >  -> ParseInfo(/cvs/CVSROOT/commitinfo, m4/examples, ALL)
 > S-> checkout (/cvs/m4/tests/Makefile.am,v, 1.13, , (function))
 > S-> checkout (/cvs/m4/tests/generate.awk,v, 1.1, , (function))
 > S-> checkout (/cvs/m4/tests/others.at,v, 1.3, , (function))
 > S-> checkout (/cvs/m4/tests/testsuite.at,v, 1.3, , (function))
 >  -> ParseInfo(/cvs/CVSROOT/commitinfo, m4/tests, ALL)
 >  -> ParseInfo(/cvs/CVSROOT/verifymsg, m4, not ALL)

        I see you are still using the old repository access with a single
CVSROOT for all software. Could you change to 
"subversions.gnu.org:/cvsroot/m4 co m4" instead ?

        In order to avoid that kind of lossage, I could kill the compatibility
hack. However, that would mean that all m4 developers still using 
"subversions.gnu.org:/cvs co m4" will face an error message. Let me know
what you prefer.

        Anyway, this is the reason why your commits do not trigger a
mail to the list.

        Cheers,

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
24 av Secretan         http://www.senga.org/      address@hidden
75019    Paris         Tel: 33 1 42 45 09 16        address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt