In the interim there has been one minor patch that addresses icon
spacing for executors in vertical panels.  FreeBSD bugzilla has no
reports for code base 16.6.  16.6.1 just addressed a regression in the
Debian Build code.  There may be a newer release tag in the upcoming
weeks.
From an OpenBSD standpoint, the port is cleaner and more intuitive -
should be easier to maintain going forward.  I also think it is likely
that the next release will be very close to the upcoming ports freeze.
My intent would be to update the next release tag in 6.5

-Scott H.


On Sep 16, 2018: 09:58, Brian Callahan wrote:

On 09/05/18 00:56, Heppler, J. Scott wrote:
Prior posts had two mistakes with the patchs.  The line count was off
and the first correction had a typo exampls now corrected to examples.
On top of that, I was doing something wrong with cvs diff - the
corrected patches were not showing up in the *diff.

Runs on my current amd64 openbox wm.

Anyway this should be good.  Sorry for the noise


Works for me too. OK for me if someone wants to commit (or let me know and I'll commit).

~Brian


On Aug 30, 2018: 18:46, Brian Callahan wrote:

On 08/30/18 00:23, Heppler, J. Scott wrote:

After I uploaded the v2 diff, it occurred to me that PKGNAME would not
be needed if I used the 16.6.1 tag.

The attached diff removes PKGNAME.  Builds/Runs -current/amd64 openbox.

Scott

I think this is right. Though when I ran `make update-patches` one of the patches got regen'd so it'll get committed with that little tweak.

Anyone want to give an ok?

~Brian



--
J. Scott Heppler

Penguin Innovations

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

NOTICE: This e-mail message and any attachments may
contain legally privileged and confidential information intended
solely for the use of the intended recipients. If you are not an
intended recipient, you are hereby notified that you have
received this message in error and any review, dissemination,
distribution, copying, or other unauthorized use of this email
and any attachment is strictly prohibited. If you have received
this email in error, please notify the sender immediately and
delete the message and any attachments from your system.

Reply via email to