From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: What's up? Not much.
Date: 03 Jan 1996 10:58:41 +0100 [thread overview]
Message-ID: <sphxwqem.fsf@bjob.no> (raw)
In *rare* moment of confusion on my part (hark! cough!) I sort of
ordered non-changable plane tickets that return me to Oslo, like, 10
days after I want to go back. So I'll probably be even more sluggish
than usual in responding to mail. I don't even have a modem here, so
I can't read news. *sob*.
But I've borrowed a machine (Windos 95 -- yuck!) and I have Emacs, so
I'll survive. Or at least I hope so.
So happy new year! And the feature freeze will start when I get to
Oslo, I guess, which is just 10 short days away.
--
Lars Magne Ingebrigtsen * larsi@ifi.uio.no
(a red leaf that falls from the purple tree)
reply other threads:[~1996-01-03 9:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=sphxwqem.fsf@bjob.no \
--to=larsi@ifi.uio.no \
/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).