From: Matthew Wilcox <matthew@wil.cx>
To: Alan Modra <alan@linuxcare.com.au>
Cc: David Huggins-Daines <dhd@linuxcare.com>,
parisc-linux@thepuffingroup.com, parisc@lists.linuxcare.com
Subject: Re: Incompatibility of PIC and non-PIC
Date: Sat, 19 Aug 2000 22:43:36 -0400 [thread overview]
Message-ID: <20000819224336.G32273@vodka.thepuffingroup.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0008201303120.26467-100000@front.linuxcare.com.au>; from Alan Modra on Sun, Aug 20, 2000 at 01:07:13PM +1000
On Sun, Aug 20, 2000 at 01:07:13PM +1000, Alan Modra wrote:
> On 19 Aug 2000, David Huggins-Daines wrote:
>
> > This chunk needs to also check for undefined symbols, it seems.
> > Here's a better one:
>
> cvs update. I think I've done things properly this time, although you'll
> no doubt find some silly bugs left when you actually run code on real
> hardware.
>
> BTW, Adding "-p" to your diff options would be a good idea.
so here's a .cvsrc file which should help people:
cvs -z3 -q
diff -uNp
update -Pd
rm -f
btw, is there any option to cvs diff which produces files which can be
applied by any known version of patch? in my experience, patch can't
find files specified by Index: lines _unless_ both the +++ and the ---
files can't be found -- which is rarely the case with common names such
as Makefile or ChangeLog. I hacked a copy of patch myself to apply one
of the cvs diff patches you posted here, but there surely has to be a
better way (complaining to Paul Eggert that while patch may or may not be
POSIX or GNU compliant it isn't _USEFUL_ may be the right answer here :-)
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2000-08-20 3:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-17 22:25 [parisc-linux] Incompatibility of PIC and non-PIC David Huggins-Daines
2000-08-18 0:12 ` Alan Modra
2000-08-18 14:29 ` Alan Modra
2000-08-18 17:25 ` David Huggins-Daines
2000-08-18 20:14 ` David Huggins-Daines
2000-08-18 23:35 ` Alan Modra
2000-08-19 5:29 ` Alan Modra
2000-08-21 17:46 ` David Huggins-Daines
2000-08-21 19:09 ` David Huggins-Daines
2000-08-21 23:39 ` Alan Modra
2000-08-19 22:00 ` David Huggins-Daines
2000-08-20 3:07 ` Alan Modra
2000-08-20 2:43 ` Matthew Wilcox [this message]
2000-08-20 4:19 ` Alan Modra
2000-08-21 13:41 ` David Huggins-Daines
2000-08-21 13:38 ` David Huggins-Daines
[not found] <alan@linuxcare.com.au>
2000-08-23 8:49 ` Tor Arntsen
2000-08-23 9:49 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2000-08-23 10:31 Tor Arntsen
2000-08-23 10:46 ` Alan Modra
2000-08-23 11:26 Tor Arntsen
2000-08-23 13:51 ` Matthew Wilcox
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=20000819224336.G32273@vodka.thepuffingroup.com \
--to=matthew@wil.cx \
--cc=alan@linuxcare.com.au \
--cc=dhd@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=parisc@lists.linuxcare.com \
/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