Summary: | freebsd-update(8) refers to stale releases | ||
---|---|---|---|
Product: | Documentation | Reporter: | Mark Linimon <linimon> |
Component: | Manual Pages | Assignee: | Ed Maste <emaste> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | cperciva, doc, emaste, ygy |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Mark Linimon
![]() ![]() I don't think we should update this every time a new version is available, as it only serves as an example. Though, 12.0-CURRENT and 10.3-STABLE do not exist anymore, so I understand that this part is technically not correct. Should we switch to more general version references instead (e.g. A.B-STABLE)? A commit references this bug: Author: emaste Date: Tue Mar 5 19:17:24 UTC 2019 New revision: 344818 URL: https://svnweb.freebsd.org/changeset/base/344818 Log: freebsd-update.8: update example to contemporary versions PR: 235761 Reported by: linimon MFC after: 1 week Changes: head/usr.sbin/freebsd-update/freebsd-update.8 (In reply to Guangyuan Yang from comment #1) I agree we don't want to start editing this on every release, but I think it wouldn't be onerous to do it once per major release, and having concrete examples makes it more understandable for users. We could just add this to (the/a) list of files to edit per year/release/etc. A commit references this bug: Author: emaste Date: Tue Mar 12 17:03:59 UTC 2019 New revision: 345071 URL: https://svnweb.freebsd.org/changeset/base/345071 Log: MFC r344818: freebsd-update.8: update example to contemporary versions PR: 235761 Reported by: linimon Changes: _U stable/12/ stable/12/usr.sbin/freebsd-update/freebsd-update.8 A commit references this bug: Author: emaste Date: Tue Mar 12 17:04:48 UTC 2019 New revision: 345072 URL: https://svnweb.freebsd.org/changeset/base/345072 Log: MFC r344818: freebsd-update.8: update example to contemporary versions PR: 235761 Reported by: linimon Changes: _U stable/11/ stable/11/usr.sbin/freebsd-update/freebsd-update.8 |