CVS anomaly: gcc/f/intdoc.texi

[Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>]

I swear I have never ever touched that file (gcc/f/intdoc.texi) in any
way, let alone modified it, yet it started showing up as modified when
I did my regular `cvs update`.

What's going on here? This never happened to me before and I've now
been using egcs-CVS for half a year...

(I have not switched to the egcs-1.1 branch or anything similiar, if
that matters.)

Gerald


markab[53]:/sw/swtest/egcs/SOURCETREE/egcs/gcc/f% cvs update intdoc.texi
M intdoc.texi
markab[54]:/sw/swtest/egcs/SOURCETREE/egcs/gcc/f% cvs status intdoc.texi
===================================================================
File: intdoc.texi       Status: Locally Modified

   Working revision:    1.11
   Repository revision: 1.11
/egcs/carton/cvsfiles/egcs/gcc/f/intdoc.texi,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

markab[55]:/sw/swtest/egcs/SOURCETREE/egcs/gcc/f% cvs diff intdoc.texi
Index: intdoc.texi
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/f/intdoc.texi,v
retrieving revision 1.11
diff -r1.11 intdoc.texi
5457,5459c5457,5459
< On some systems (specifically SCO) it may be necessary to link the
< `socket' library if you call this routine, i.e.@: add @samp{-lsocket}
< to the @code{g77} arguments.
---
> On some systems (specifically SCO) it might be necessary to link the
> ``socket'' library if you call this routine, i.e.@: append
> @samp{-lg2c -lsocket -lm} to the @code{g77} arguments.
5490,5492c5490,5492
< On some systems (specifically SCO) it may be necessary to link the
< `socket' library if you call this routine, i.e.@: add @samp{-lsocket}
< to the @code{g77} arguments.
---
> On some systems (specifically SCO) it might be necessary to link the
> ``socket'' library if you call this routine, i.e.@: append
> @samp{-lg2c -lsocket -lm} to the @code{g77} arguments.