root@libove.UUCP (Jay M. Libove) (10/07/88)
One feature that would be a nice addition to the "patch" software, which is already one of the most useful pieces of software I have ever seen, thanks Larry! - would be an option to pause on patch rejection, so that the executing user would be made explicitly aware of what went wrong, or better yet a logfile option to log failed patches, putting the bad patch, the source file name, in the logfile. What do you all think? Larry, you out there? Thanks again! -- Jay Libove ARPA: jl42@andrew.cmu.edu or libove@cs.cmu.edu 5731 Centre Ave, Apt 3 BITnet: jl42@andrew or jl42@drycas Pittsburgh, PA 15206 UUCP: uunet!nfsun!libove!libove or (412) 362-8983 UUCP: psuvax1!pitt!darth!libove!libove
lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) (10/25/88)
In article <168@libove.UUCP> root@libove.UUCP (Jay M. Libove) writes:
: One feature that would be a nice addition to the "patch" software, which
: is already one of the most useful pieces of software I have ever seen,
: thanks Larry! - would be an option to pause on patch rejection, so that
: the executing user would be made explicitly aware of what went wrong,
: or better yet a logfile option to log failed patches, putting the bad
: patch, the source file name, in the logfile.
:
: What do you all think? Larry, you out there?
Hi, just got back from England...
I think you could do most of that right now by wrapping it in a shell script
that checks the status and looks for reject files.
Larry Wall
lwall@jpl-devvax.jpl.nasa.gov