Path: utzoo!mnetor!uunet!husc6!hao!ames!elroy!devvax!lwall
From: lwall@devvax.JPL.NASA.GOV (Larry Wall)
Newsgroups: comp.sources.bugs
Subject: Re: perl patch 18 makes perl uncompilable
Message-ID: <1328@devvax.JPL.NASA.GOV>
Date: 16 Feb 88 21:08:33 GMT
References: <2641@dciem.UUCP> <513@hscfvax.harvard.edu>
Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall)
Organization: Jet Propulsion Laboratory, Pasadena, CA.
Lines: 16

In article <513@hscfvax.harvard.edu> mohamed@hscfvax.harvard.edu (Mohamed_el_Lozy) writes:
: How useful is the verbose output of patch?  Does ity serve any purpose (other
: than as a debugging tool while patch was being developped)?  Is there a
: way to shut it up?
: 
: My feeling is that optimal behavior would be no output other than a patch
: succeedded or patch failed message.  That would be impossible to miss.  Even
: more in the UNIX tradition would be no message at all unless it failed.

Try -s.  That's why it's there.  It's even documented.

If you're going to apply a lot of patches you probably want to put it in a loop
that checks the exit status each time and refuses to go on if there's a problem.

Larry Wall
lwall@jpl-devvax.jpl.nasa.gov