From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ipaq dual pcmcia sleeve unsupported? (or so it seems)
Date: Thu, 17 Oct 2002 10:29:01 +0200 [thread overview]
Message-ID: <bbb79fbc3c6e18a97b2acc569cad64bc@plan9.escet.urjc.es> (raw)
> I took nemo's tar ball, and built on that,
> but needed tiny changes to be able compile his code.
Yep. The bitsy tar ball in the web is out of date; it corresponds
to a few updates ago. I'll update it as soon as I can, but probably
not this week. Sorry.
next reply other threads:[~2002-10-17 8:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 8:29 Fco.J.Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 15:01 Fco.J.Ballesteros
2002-10-17 15:48 Fco.J.Ballesteros
2002-10-17 16:05 ` Stephen Parker
2002-10-17 14:43 Fco.J.Ballesteros
2002-10-17 14:16 Sape Mullender
2002-10-17 14:42 ` Stephen Parker
2002-10-16 22:01 presotto
2002-10-16 22:19 ` Axel Belinfante
2002-10-16 22:47 ` Axel Belinfante
2002-10-13 14:11 Sape Mullender
2002-10-16 21:48 ` Axel Belinfante
2002-10-17 13:24 ` Axel Belinfante
2002-10-13 12:46 Axel Belinfante
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=bbb79fbc3c6e18a97b2acc569cad64bc@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).