os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Change every outstanding 'short' link to the FAQ or Handbook to use

Browse source 
the now mandatory 'long' format.  This should catch everything, with
the exception of the release notes.
This commit is contained in:
Nik Clayton 2002-06-29 09:07:09 +00:00
parent 94aa190a2f
commit dd365111ba
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=13507
26 changed files with 94 additions and 94 deletions
Download patch file Download diff file Expand all files Collapse all files

6
share/sgml/advisories.xml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/security/security.sgml,v 1.99 2002/06/26 19:09:37 nectar Exp $">
<!ENTITY date "$FreeBSD: www/en/security/security.sgml,v 1.100 2002/06/27 11:43:33 nectar Exp $">
<!ENTITY title "FreeBSD Security Information">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $FreeBSD: www/en/security/security.sgml,v 1.99 2002/06/26 19:09:37 nectar Exp $ -->
<!-- $FreeBSD: www/en/security/security.sgml,v 1.100 2002/06/27 11:43:33 nectar Exp $ -->
<html>
&header;
@ -83,7 +83,7 @@ At this time, security advisories are being released for:
to upgrade to one of the supported releases mentioned above.</P>
<P>Like all development efforts, security fixes are first brought into
the <A HREF="../handbook/cutting-edge.html#CURRENT">FreeBSD-current</A> branch.
the <A HREF="../doc/en_US.ISO8859-1/books/handbook/cutting-edge.html#CURRENT">FreeBSD-current</A> branch.
After a couple of days and some testing, the fix is retrofitted into
the supported FreeBSD-stable branch(es) and an advisory is then sent
out.</P>