Rather than having everyone receiving all cvs-all messages, why not create
a mail address that filters all mail received from cvs-all by branch, and
sends them to the apropriate list. Create the lists, and add this address
to the cvs-all list, and you have a functioning list per branch. The total
work involved must be less than everyone doing it individually.
Tim.
"Brandon D. Valentine" wrote:
> On Sun, 30 Apr 2000, James Housley wrote:
>
> >At least one person, sorry I forget who, posted that they use procmail
> >to filter it out. I and probably others use procmail, but at the
> >simplest level. Would someone be willing to post the portion they use
> >to process -stable from cvs-all
> >Keywords for searching: procmail cvs stable commit
>
> Absolutely, you're not the only person to ask this, several others
> mailed me in private asking how to do it. Try the following recipe to
> catch all RELENG_4 commits:
>
> :0B:
> * ^Sender:.*[EMAIL PROTECTED]
> * ^.*(Branch: RELENG_4)
> fbsd-cvs-releng4
>
> Obviously you can change the folder name to wherever you would prefer
> the messages to land. Here's one to catch commits to RELENG_4 *and*
> RELENG_3:
>
> :0B:
> * ^Sender:.*[EMAIL PROTECTED]
> * ^.*(Branch: RELENG_4)|.*(Branch: RELENG_3)
> fbsd-cvs-stable
>
> Or say you only wanted stable, kernel commits:
>
> :0B:
> * ^Sender:.*[EMAIL PROTECTED]
> * ^.*(Branch: RELENG_4)|.*(Branch: RELENG_3)
> * ^Subject:.*cvs commit: src/sys
> fbsd-cvs-stable-sys
>
> You get the idea.
>
> Brandon D. Valentine
> --
> [EMAIL PROTECTED] Illegitimi non carborundum.
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
