linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Lou Langholtz <ldl@chpc.utah.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.whatever and hfs
Date: Fri, 15 Oct 1999 00:55:25 -0600	[thread overview]
Message-ID: <3806CFDC.DE76238C@chpc.utah.edu> (raw)


Has anybody picked up UFS then to implement it under 2.3+? I'm asking
cause if I can manage to download and build the latest 2.3 from
cvs.on.openprojects.net, I'll try hacking HFS if nobody else has already
started/done the work. Thanks.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~1999-10-15  6:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-15  6:55 Lou Langholtz [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-09-21  1:54 2.3.whatever and hfs David Riley
1999-09-21  3:23 ` David D. Kilzer
1999-09-21  6:05   ` Sriranga Veeraraghavan
1999-09-21  6:17   ` Martin Costabel
1999-09-22 12:28     ` Brad Boyer

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=3806CFDC.DE76238C@chpc.utah.edu \
    --to=ldl@chpc.utah.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).