Date: Tue, 22 Aug 2023 09:05:11 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 269810] ports-mgmt/pkg: how to restore pkg database Message-ID: <bug-269810-32340-tDj3OX8Zhu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-269810-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-269810-32340@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=3D269810 --- Comment #8 from Graham Perrin <grahamperrin@freebsd.org> --- Back closer to topic, in an effort to avoid confusion: removal of <https://github.com/freebsd/freebsd-doc/pull/117>; from the See Also field of this bug report was not specific to this report. This one removal was, naturally, consequent to a broader request for (indiscriminate) closure of = all my PRs in that area.=20 ---- Back on topic, for readers who may be unfamiliar with features of GitHub:=20 .diff and .patch files do remain available, as shown below (their=20 URLs are disallowed for See Also purposes). <https://github.com/freebsd/freebsd-doc/pull/117.diff>; <https://github.com/freebsd/freebsd-doc/pull/117.patch>=20=20=20=20=20 ---- Looking ahead, more generally: Bugmeister might like to advise whether it's appropriate to have the 'needs-patch' keyword in situations such as this, w= here a patch file is available but not directly attached. Reports with no non-obsolete patch attached can _not_ be found by queries such as this:=20 <https://bugs.freebsd.org/bugzilla/buglist.cgi?cmdtype=3Drunnamed&namedcmd= =3Dall%20open%20reports%20with%20a%20non-obsolete%20patch%2C%20by%20assigne= e> > all open reports with a non-obsolete patch, by assignee For readers to _not_ misconstrue needs-patch as no-patch, my instinct is to misuse the deprecated 'patch' keyword ;-) Yep, the one that I long ago batch-applied before the deprecated keyword was marked as such. Oops. Of course, I'll not apply it :-) This discussion can continue in private. No rush. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. 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-269810-32340-tDj3OX8Zhu>