Date: Sat, 1 Jun 2002 05:27:45 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: "Brandon D. Valentine" <bandix@geekpunk.net> Cc: Matt Dillon <dillon@FreeBSD.org>, freebsd-hackers@FreeBSD.org Subject: Re: Adding diffs to commit-mail on the fly Message-ID: <20020601022745.GA13090@hades.hell.gr> In-Reply-To: <20020531211416.J199-100000@leto.homeportal.2wire.net> References: <20020601020705.GC4572@hades.hell.gr> <20020531211416.J199-100000@leto.homeportal.2wire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-05-31 21:18 -0500, Brandon D. Valentine wrote: >On Sat, 1 Jun 2002, Giorgos Keramidas wrote: >>On 2002-05-31 20:53 -0500, Brandon D. Valentine wrote: >>> Assuming your script works, here's the procmail hoodoo: >>> >>> :0 fw >>> * ^List-Id: <cvs-all.FreeBSD.ORG> >>> | /path/to/filter/script >> >>The problem with this is that I would have to hardwire the output >>folder name to the script, or pass it as a parameter. I've found two >>answers until now, by reading my manpages [beats head]. One is: > > Nonsense. With the rule I gave you your script should take the message > on stdin, modify it, and spit it back out on stdout where it will > continue to fall through the procmail rules. That's what the 'f' option > at the start of the rule is all about. You end up with two succesive > rules like this: > > :0 fw > * ^List-Id: <cvs-all.FreeBSD.ORG> > | /path/to/filter/script > > :0: > *^ List-Id: <cvs-all.FreeBSD.ORG> > cvs-all > > Make sense? Indeed. Brain cells shutting down already. I shouldn't read procmail rules after I get sleepy. The 'f' flag of procmail seems like, aw mee gods, so fine ;-))) - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020601022745.GA13090>