From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: pbm trying to patch 21.1 into 21.2
Date: Wed, 04 Sep 2002 14:10:36 +0200 [thread overview]
Message-ID: <vafd6ruoszn.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: al46k0$hgm$1@reader1.panix.com
dkcombs@panix.com (David Combs) writes:
> Meanwhile, I've grepped and done strings | grep
> on that "Looks like" and can find it nowhere.
>
> From all the patches and diff-running you've done
> to emacs over the years, do you have *any* clue
> as to where that error-string comes from?
The "Looks like" looks like it's coming from the program "patch".
It's not an error. Just a piece of information.
You can also look at the patch (diff) yourself if it's a new-style
context diff. Then you know whether the "patch" program has made the
right decision.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
prev parent reply other threads:[~2002-09-04 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 19:32 pbm trying to patch 21.1 into 21.2 David Combs
2002-09-03 21:52 ` Kai Großjohann
2002-09-04 5:44 ` David Combs
2002-09-04 12:10 ` Kai Großjohann [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vafd6ruoszn.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).