Page MenuHomeFreeBSD

misc/mbuffer: Update to 20210328
ClosedPublic

Authored by loader on May 18 2021, 5:57 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jan 25, 7:57 PM
Unknown Object (File)
Fri, Jan 24, 7:01 PM
Unknown Object (File)
Jan 21 2025, 12:04 PM
Unknown Object (File)
Dec 9 2024, 4:18 PM
Unknown Object (File)
Nov 30 2024, 3:21 AM
Unknown Object (File)
Nov 27 2024, 7:15 AM
Unknown Object (File)
Nov 27 2024, 7:15 AM
Unknown Object (File)
Nov 27 2024, 7:15 AM
Subscribers

Details

Summary
misc/mbuffer: Update to 20210328

- Update to 20210328
- Switch to USES=autoreconf gmake instead of patching configure and Makefile.in
- Take maintainership

Reviewed_by:	koobs
Approved by:	koobs (ports, mentor, implicit)
Differential_Revision: D30338
MFH:		No (feature release)
Test Plan
  • portlint: OK (looks fine.)
  • testport: OK (poudriere: 140006, [armv7,aarch64,i386,amd64], tested)

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

loader retitled this revision from Proposed commit log message: ``` misc/mbuffer: Update to 20210328 to misc/mbuffer: Update to 20210328.May 18 2021, 6:00 PM
loader edited the summary of this revision. (Show Details)
koobs edited the summary of this revision. (Show Details)

I've tweaked the commit log message. This change also comes under implicit

This revision is now accepted and ready to land.May 19 2021, 1:55 AM
This revision was automatically updated to reflect the committed changes.

One other note. When taking maintainer'ship or when combining multiple changes, land all changes that can be MFH'd first , and the version update separately.

This ensures ports in all branches have the same maintainer

One other note. When taking maintainer'ship or when combining multiple changes, land all changes that can be MFH'd first , and the version update separately.

This ensures ports in all branches have the same maintainer

one commit to update the MAINTAINER and bump up PORTREVISION, and MFH this commit.
then another commit for the version update and no MFH, right?

Yep, rule of thumb:

  • Mergeable commits first
  • Non mergeable commits last

Mergeable commits:

  • Consistent metadata (maintainer, etc)
  • Bugfixes

Yep, rule of thumb:

  • Mergeable commits first
  • Non mergeable commits last

Mergeable commits:

  • Consistent metadata (maintainer, etc)
  • Bugfixes

Okay, thanks for the note.