In changed from changegroup.notify to incoming.notify. Let's see how that goes. (The most recent push about m5ops stuff was a push of two changesets with incoming.notify)
Nate On Fri, Jul 11, 2008 at 9:38 AM, Steve Reinhardt <[EMAIL PROTECTED]> wrote: > On a separate but related note, does anybody care if we change the > notify template to include the full commit description and not just > the first-line summary? As far as I can tell, the single-changeset > template does this already, but since we're using the changegroup > hook, it just uses the first line to "save space" even when there's > only one changeset in the changegroup... which seems silly since if > we're concerned about space I'd rather lop off the diff than the extra > few lines of the description. > > Steve > > On Fri, Jul 11, 2008 at 9:12 AM, nathan binkert <[EMAIL PROTECTED]> wrote: >> Ali recently updated mercurial and it broke the notify extension (the >> thing that sends out e-mails). This is because we were using a >> slightly hacked up version of it due to a bug in the one distributed >> with hg. I changed things so that we're now using the standard notify >> extension and it seems to work. If anyone does a push and gets an >> error message, or doesn't see their e-mail, please send a message to >> m5-dev. >> >> Thanks, >> Nate >> _______________________________________________ >> m5-dev mailing list >> [email protected] >> http://m5sim.org/mailman/listinfo/m5-dev >> > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
