Date: Sun, 23 Oct 2022 10:50:10 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 206165] resolv.conf(5) is missing documentation on options Message-ID: <bug-206165-9-V8VIcwsmd9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206165-9@https.bugs.freebsd.org/bugzilla/> References: <bug-206165-9@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=3D206165 Graham Perrin (non-committing) <grahamperrin@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grahamperrin@gmail.com --- Comment #7 from Graham Perrin (non-committing) <grahamperrin@gmail.com>= --- Re: <https://reviews.freebsd.org/D37086>, the 'patch' keyword (above) can/should be removed.=20 Bug 227147 will gain a hint of:=20 * how to seek bug reports where an attachment is definitely a patch.=20 bcr@ would you like to make yourself the assignee? Also, add the URL of the review to the See also: field.=20 Thanks. (In reply to O. Hartmann from comment #5) This Bugzilla includes more than a thousand non-resolved reports that use t= he (deprecated) patch keyword. For each such report that is relatively old, th= ere might be any number of reasons for lack of progress.=20 I think, it'll be useful to discuss generally =E2=80=93 without singling ou= t this bug 206165 =E2=80=93 can I suggest the freebsd-questions mailing list? Or IRC, = if you prefer: aim for the #bugs channel.=20 Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206165-9-V8VIcwsmd9>