Index | Thread | Search

From:
Daniel Jakots <danj@chown.me>
Subject:
Re: [UPDATE] net/miniflux 2.2.12 -> 2.2.13
To:
Igor Zornik <mocheryl@mocheryl.org>
Cc:
OpenBSD ports <ports@openbsd.org>
Date:
Thu, 16 Oct 2025 22:27:28 -0400

Download raw body.

Thread
On Sat, 04 Oct 2025 11:03:54 +0200, Igor Zornik <mocheryl@mocheryl.org>
wrote:

> On Thu, 2025-10-02 at 17:32 -0400, Daniel Jakots wrote:
> > On Wed, 01 Oct 2025 19:04:46 +0200, "Igor Zornik"
> > <mocheryl@mocheryl.org> wrote:
> >
> > Looks good (with 2 minor details), but unfortunately the tree is now
> > locked. It will wait until the unlock, unless I'm missing something
> > that makes the update important?
> >   
> 
> I see. In my defense, the submission was made prior to lock
> announcement, so I thought it was still fair game.

No worry, it was just to explain that it wouldn't be committed until
the port tree reopens ;)

naddy gave the green light so I just committed the update, thanks!

> When I check how other ports are done, what I generally see is
> <variable><space><equal sign><tab><value>, so that's the convention
> I follow when creating new ports or modifying existing ones. Was my
> assumption incorrect?

That's correct. There are (or used to? I'm not paying attention to that
many different ports nowadays) some small stylistic variations but your
diff was fine :)

Cheers,
Daniel