From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 Ports rc under NetBSD
Date: Mon, 26 Jun 2006 14:09:58 -0400 [thread overview]
Message-ID: <20060626180958.GA48313@mero.morphisms.net> (raw)
In-Reply-To: <20060626194512.89fa4312.20h@r-36.net>
On Mon, Jun 26, 2006 at 07:45:12PM +0200, Christoph Lohmann wrote:
> The problem is a bit different. In NetBSD getdirentries() is obsolete,
> so $PLAN9/src/lib9/dirread.c is wrong. Here is a diff to get it to work
> with NetBSD. Attached is a diff to dirread.c, that gets it to work again.
>
> Russ, should I send a patch for p9p?
I've applied the patch for now. When did NetBSD start
using the new interface -- do we need to worry about
backwards compatibility?
next prev parent reply other threads:[~2006-06-26 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 16:23 Matthias Teege
2006-06-26 17:44 ` Christoph Lohmann
2006-06-26 17:45 ` Christoph Lohmann
2006-06-26 18:09 ` William Josephson [this message]
2006-06-26 18:23 ` Christoph Lohmann
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=20060626180958.GA48313@mero.morphisms.net \
--to=jkw@eecs.harvard.edu \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).