Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 May 2021 12:45:26 +0200
From:      Willem Jan Withagen <wjw@digiware.nl>
To:        Chris <portmaster@bsdforge.com>, "Julian H. Stacey" <jhs@berklix.com>
Cc:        Jan Beich <jbeich@freebsd.org>, freebsd-ports <freebsd-ports@freebsd.org>
Subject:   Re: Is there a way to subscribe to the commit messages for only ports you maintain?
Message-ID:  <6c3baa80-88f3-f5ef-bad0-4e0b226a7ecc@digiware.nl>
In-Reply-To: <4f9fdb113c1d23ae9e06a3608e119e87@bsdforge.com>
References:  <202105180117.14I1H3LX072989@fire.js.berklix.net> <4f9fdb113c1d23ae9e06a3608e119e87@bsdforge.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 18-5-2021 03:56, Chris wrote:
> On 2021-05-17 18:17, Julian H. Stacey wrote:
>> Chris wrote:
>>> On 2021-05-17 16:30, Jan Beich wrote:
>>> > Chris <portmaster@bsdforge.com> writes:
>>> >
>>> >> I'd like to subscribe to the commit messages
>>> >> ( dev-commits-ports-all )
>>> >> but only receive messages that affect me -- the
>>> >> ports I currently maintain. Is it possible? Or
>>> >> am I just dreaming? ;-)
>>> >
>>> > No clue but I use Herald rules for something similar.
>>> Thanks for the hints, Jan. :-)
>>
>> Herald ? Nothing from
>> https://www.freebsd.org/cgi/ports.cgi?query=herald&stype=all&sektion=all
>> ...
>>   https://en.wikipedia.org/wiki/Phabricator
>> ...
>> https://cgit.freebsd.org/ports/tree/devel/phabricator/pkg-descr
>>
>>
>> I'd use /usr/ports/mail/procmail
>> https://lists.freebsd.org/pipermail/dev-commits-ports-all/2021-May/date.html
>> ~/.procmailrc example:
>> :0 H
>> * ^Sender: owner-dev-commits-ports-all@freebsd.org
>>   {
>>   :0 H
>>   * ^Subject: git: .+ sysutils/rubygem-bolt
>>   | $RCVSTORE +dir_of_ports_you_might_maintain
>>   :0 H
>>   * ^Subject: git: .+ x11/xterm
>>   | $RCVSTORE +another_dir_of_ports_you_might_maintain
>>   }
>>
>> or eg: # mkdir ~/Mail/your_ports
>>   :0 H
>>   * ^Sender: owner-dev-commits-ports-all@freebsd.org
>>   * ^Subject: git: .+
>> (archivers/bzip|audio/pocketsphinx|audio/snd|comms/pr|comms/sms_client|databases/pgaccess|devel/c2mdoc|devel/compiz-bcop|devel/ecgi|devel/codeville|devel/frink|dns/dnscheckengine|dns/ldapdns|graphics/gdtclft|graphics/gimmage|graphics/repng2jpeg|graphics/urt|lang/picoc|net/beacon|net/openradius|net/spread|net/wackamole|net-im/mbpurple|sysutils/cdroot|sysutils/ffs2recov|sysutils/rsyncbackup|textproc/asm2html|textproc/smi|textproc/sansi|www/spreadlogd|www/ttf2eot|x11/wmblob|x11/xvt|x11-themes/kde-icons-graphite-rade8|x11-toolkits/iwidgets|x11-wm/icewm) 
>>
>>   | $RCVSTORE +your_ports
>
> Wow! Thanks Julian. You even did all my homework for me.! ;-)
> In fact I think your re would even satisfy Herald.

Yup, this is a great example.
I had been wining about the same problem in private, but dit not even 
realize that this list is available.

Perhaps this piece of code and suggestion for commits-ports-all could go 
into the porters manual?

--WjW



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6c3baa80-88f3-f5ef-bad0-4e0b226a7ecc>