Date: Thu, 24 Feb 2022 01:26:44 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 262148] devel/git-review: Fails to run with git >= 2.3.40: fatal: --preserve-merges was replaced by --rebase-merges Message-ID: <bug-262148-7788-5UqGCSKcoA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262148-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-262148-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262148 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback- |maintainer-feedback?(dereck | |son@gmail.com) --- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to dereckson from comment #4) Note its preferable to fix bugs only and separately in quarterly (where possible), independently of whether a new release is available or not, such that changes can be minimized in quarterly, unless those later release(s) a= re also bugfix *only*, in which case, they can and should be merged also. ^Triage: Maintainer feedback provided (set to +). This is separate from pat= ch approval. If every release between port current version and latest (2.2.0) are bugfix= es only, we can depend on bug 262164, otherwise the patch here is more appropr= iate to commit and merge first, before and separately from the version update. @Maintainer Can you clarify the nature of all releases after the current po= rt version (bugfix only or additional features as well?) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262148-7788-5UqGCSKcoA>