Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alex deVries <adevries@engsoc.carleton.ca>, linux@cthulhu.engr.sgi.com
Subject: Re: Update ...
Date: Thu, 4 Dec 1997 23:18:21 +0100	[thread overview]
Message-ID: <19971204231821.08074@uni-koblenz.de> (raw)
In-Reply-To: <m0xdbxc-0005FsC@lightning.swansea.linux.org.uk>; from Alan Cox on Thu, Dec 04, 1997 at 02:09:00PM +0000

On Thu, Dec 04, 1997 at 02:09:00PM +0000, Alan Cox wrote:

> > Can someone _please_ break my cycle by uploading their functional libc?
> > Please? If I get it, and can become a productive member of society again.
> 
> I think we are all in the same boat but I've been waiting cos Ralf did say
> he doesnt get to upload tons of stuff any time he wants. 

Yes.  Basically the problem is that I have to carry all the stuff to
the university for uploading.  Everything else would be pretty insane
over a 28.8k line at German phone rates.  Right now I already have about
120mb of pending uploads and the Indy is still compiling ...

Note that only publishing libc wouldn't do the job.  Some libc bugs
also affect the part of libc that are being linked statically into
executables.

  Ralf

  parent reply	other threads:[~1997-12-04 22:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-04  1:08 Update ralf
1997-12-04  2:36 ` Update Alex deVries
1997-12-04  3:05   ` Update ralf
1997-12-04  3:37     ` Update Alex deVries
1997-12-04  4:27       ` Update ralf
1997-12-04  4:33       ` Update ralf
1997-12-04 14:19         ` Update Alan Cox
1997-12-04 14:09   ` Update Alan Cox
1997-12-04 14:09     ` Update Alan Cox
1997-12-04 22:18     ` ralf [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-12-05 17:07 Update ralf

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=19971204231821.08074@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=adevries@engsoc.carleton.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux@cthulhu.engr.sgi.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