Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Mike Shaver <shaver@neon.ingenia.ca>
To: ariel@cthulhu.engr.sgi.com
Cc: mgix@nothingreal.com, linux@cthulhu.engr.sgi.com
Subject: Re: Step by step of my experience
Date: Thu, 23 Oct 1997 02:24:39 -0400 (EDT)	[thread overview]
Message-ID: <199710230624.CAA13875@neon.ingenia.ca> (raw)
In-Reply-To: <199710230010.RAA272545@oz.engr.sgi.com> from Ariel Faigon at "Oct 22, 97 05:10:33 pm"

Thus spake Ariel Faigon:
> Actually, it is Mike Shaver, we talked about this one pretty
> recently, he is pretty busy but when he find some time to fix
> this it would make things much simpler.

I've managed to procure a temporary Indy at work now, so I should be
able to start hacking on EFS again early next week.  I actually have
better support already than that kernel would indicate, but I haven't
committed all of the changes yet (I don't think).

I'll clean up my current support tomorrow or Friday, and then I'll
check it in and coerce Miguel or Ralf into making a new test kernel
available.

Mike

-- 
#> Mike Shaver (shaver@ingenia.com) Ingenia Communications Corporation 
#>            Chief System Architect and Herder of Bits                
#>                                                                     
#> "Yoda say, `Just slap a little public key crypto into it' does not  
#>      a secure system make." -- Marcus J. Ranum (mjr@clark.net)      

  parent reply	other threads:[~1997-10-23  6:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-22 22:26 Step by step of my experience Emmanuel Mogenet
1997-10-23  0:10 ` Ariel Faigon
1997-10-23  0:10   ` Ariel Faigon
1997-10-23  6:24   ` Mike Shaver [this message]
1997-10-29 18:14   ` Alan Cox
1997-10-29 21:50     ` Miguel de Icaza
1997-10-29 22:42       ` Alan Cox
1997-10-29 22:42         ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
1997-10-24 17:07 Mike Hill
1997-10-24 21:12 ` Ralf Baechle
1997-10-24 21:12   ` Ralf Baechle

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=199710230624.CAA13875@neon.ingenia.ca \
    --to=shaver@neon.ingenia.ca \
    --cc=ariel@cthulhu.engr.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=mgix@nothingreal.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