From: <hzoli@VNET.IBM.COM> (Zoltan T. Hidvegi)
To: borsenkow.msk@sni.de
Subject: Re: Warning: patch-2.2 and zsh-3.1.2 patch
Date: Mon, 12 May 1997 14:14:48 -0400 (EDT) [thread overview]
Message-ID: <9705121815.AA22108@lotto.fishkill.ibm.com> (raw)
In-Reply-To: <Pine.SV4.3.95.970512143954.13907A-100000@itsrm1> from Andrej Borsenkow at "May 12, 97 02:51:42 pm"
Andrej Borsenkow wrote:
> Probably of some interest: I had problems with new patch 2.2. First, it
> rejects plain -p option (without operand); second, if given patch
That's bad. I've been using using patch -p for ages.
> _without_ -p option at all, it cannot find any file with pathname.
Yes, you should not use it without -p. It can patch the wrong Makefile.in
and other bad things can happen.
> patch -p0 seems to work. I don't remember, if -p0 was legal option in
> earlier versions of patch, but if yes, please, add it to your shell
> script.
Yes, -p0 was always legal, but I was always lazy to write this redundant
zero. And I'm sure that I'll keep forgetting this well after I upgrade my
patch program.
> As a side note, our shell doesn't like
> echo $errors hunk(s) failed.
> line. It complaints "syntax error: `(' unexpected". It is claimed to be
> POSIX-compliant.
Which is OK, since no other POSIX/Bourne shell can parse that line. I did
not notice this since when I tested this, the patch did not fail and this
line was never executed.
Zoltan
prev parent reply other threads:[~1997-05-12 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-12 10:51 Andrej Borsenkow
1997-05-12 11:07 ` Hrvoje Niksic
1997-05-12 18:14 ` Zoltan T. Hidvegi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9705121815.AA22108@lotto.fishkill.ibm.com \
--to=hzoli@vnet.ibm.com \
--cc=borsenkow.msk@sni.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).