🚀 go-pugleaf

	Just wondering about the following 3 failures in patch #2.  I'm
in the middle of a project so I can't take much time to try to track this
down further.  I'm wondering if others have run into this, and if it
is anything I should be worried about (if it's worth it to patch by hand
right now).  The environment is a Sun 3/280, OS 4.0 (just 4.0, it should
get upgraded very soon):

--------------------------
|
|*** /tmp/,RCSt1a00400  Fri Feb  9 13:13:14 1990
|--- mit/server/ddx/cfb/cfbrctstp8.c    Fri Feb  9 13:12:54 1990
--------------------------
Patching file mit/server/ddx/cfb/cfbrctstp8.c using Plan A...
Hunk #1 failed at 18.
Hunk #2 succeeded at 269.
1 out of 2 hunks failed--saving rejects to mit/server/ddx/cfb/cfbrctstp8.c.rej



|
|*** /tmp/,RCSt1a01657  Fri Feb  9 14:17:54 1990
|--- mit/server/ddx/mi/miwideline.c     Fri Feb  9 14:17:36 1990
--------------------------
Patching file mit/server/ddx/mi/miwideline.c using Plan A...
Hunk #1 failed at 1.
Hunk #2 succeeded at 1650 (offset -16 lines).
1 out of 2 hunks failed--saving rejects to mit/server/ddx/mi/miwideline.c.rej


|
|*** old/lib/Xt/Create.c
|--- mit/lib/Xt/Create.c
--------------------------
Patching file mit/lib/Xt/Create.c using Plan A...
Hunk #1 failed at 1.
Hunk #2 succeeded at 167.
1 out of 2 hunks failed--saving rejects to mit/lib/Xt/Create.c.rej


-- 
   dansmith@well.sf.ca.us   daniel@island.uu.net   unicom!daniel@pacbell.com
ph: (415) 332 3278 (h), 491 1000 (w) disclaimer: Island's coffee was laced :-)