Date: Thu, 4 Sep 2003 23:04:21 +0100 From: Ceri Davies <ceri@FreeBSD.org> To: doc@FreeBSD.org Subject: 3 line diff creates 700 line whitespace diff problem Message-ID: <20030904220421.GR25063@submonkey.net>
next in thread | raw e-mail | index | archive | help
--35rzUHtxHARXKmYf
Content-Type: multipart/mixed; boundary="McQJJYUzjTUqtsGv"
Content-Disposition: inline
--McQJJYUzjTUqtsGv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
jon@witchspace.com pointed out to me that the section numbers in the
IPsec section of the handbook are slightly off: 10.9.4 and 10.9.5
should really be 10.9.3.1 and 10.9.3.2.
My dilemma is that committing the attached patch to correct this will
also require that all the intervening lines (~700 of them) will need
to be indented to keep the whitespace consistent. Would a whitespace
commit of that proportion be excessive, or a necessary evil?
Ceri
--=20
User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR?
Iniaes: Sure, I can accept all forms of payment.
-- www.chatterboxchallenge.com
--McQJJYUzjTUqtsGv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="ipsec-sections.diff"
Content-Transfer-Encoding: quoted-printable
Index: chapter.sgml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/security/chapter.sg=
ml,v
retrieving revision 1.182
diff -u -r1.182 chapter.sgml
--- chapter.sgml 1 Sep 2003 23:11:15 -0000 1.182
+++ chapter.sgml 4 Sep 2003 21:58:06 -0000
@@ -3145,9 +3145,8 @@
VPN.</para>
</listitem>
</orderedlist>
- </sect2>
=20
- <sect2>
+ <sect3>
<title>Step 1: Creating and testing a <quote>virtual</quote>
network link</title>
=20
@@ -3379,9 +3378,9 @@
reversing the order of IP addresses.</para>
</listitem>
</itemizedlist>
- </sect2>
+ </sect3>
=20
- <sect2>
+ <sect3>
<title>Step 2: Securing the link</title>
=20
<para>To secure the link we will be using IPsec. IPsec provides
@@ -3814,6 +3813,7 @@
running. Machines on each network will be able to refer to one
another using IP addresses, and all traffic across the link will
be automatically and securely encrypted.</para>
+ </sect3>=20
</sect2>=20
</sect1>
=20
--McQJJYUzjTUqtsGv--
--35rzUHtxHARXKmYf
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/V7blocfcwTS3JF8RAl2gAJ9xtvF+AubfDU7ZN6euiajEMDaCtACfSTvx
+ZeYARO1hi+25WJsWKLDs7M=
=mro1
-----END PGP SIGNATURE-----
--35rzUHtxHARXKmYf--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030904220421.GR25063>