Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Mar 2026 09:04:13 +0300
From:      Gleb Popov <arrowd@freebsd.org>
To:        Alexey Dokuchaev <danfe@freebsd.org>
Cc:        Max Brazhnikov <makc@freebsd.org>, ports-committers@freebsd.org,  dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org
Subject:   Re: git: f40485c6b3d9 - main - deskutils/qownnotes: reset MAINTAINER
Message-ID:  <CALH631mgUcnXBF9Uia7X5kwmJfeHcOmVSAH%2BjR7wT8PGUxh5Zg@mail.gmail.com>
In-Reply-To: <aa-BizVyY5puYH-B@FreeBSD.org>
References:  <69af04eb.18b97.66abbd99@gitrepo.freebsd.org> <aa-BizVyY5puYH-B@FreeBSD.org>

index | next in thread | previous in thread | raw e-mail

On Tue, Mar 10, 2026 at 5:27 AM Alexey Dokuchaev <danfe@freebsd.org> wrote:
>
> On Mon, Mar 09, 2026 at 05:35:39PM +0000, Max Brazhnikov wrote:
> > commit f40485c6b3d9ec1c7b59428ac54f83448aacaa07
> >
> >   deskutils/qownnotes: reset MAINTAINER
> >
> >   The port is de facto maintained by danfe@ for several years.
>
> Yeah so you've reset it to ports@.  Please don't throw in useless
> commits which clutter commit history and don't do any good.
>
> ./danfe
>

It could've been avoided if you assumed the maintainership yourself in
past updates.
Strictly speaking you were breaking the timeout rule each time. The
established way
to counter maintainer timeout is to put a change that resets
MAINTAINER, wait 2 weeks,
then push it. You didn't care about that, but now are worrying about a
"useless" commit.


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631mgUcnXBF9Uia7X5kwmJfeHcOmVSAH%2BjR7wT8PGUxh5Zg>