From: sl@9front.org
To: 9front@9front.org
Subject: 9FRONT "ADAM BOMB" ReleasedMIME-Version: 1.0
Date: Sat, 9 Mar 2013 14:26:14 -0500 [thread overview]
Message-ID: <edc12f914fe77f4b89d896346994ec2b@9front.org> (raw)
New 9front release "ADAM BOMB" *
http://r-36.net/9front/9front-2443.e9b850eb5026.iso.bz2.torrent
http://r-36.net/9front/9front-2443.e9b850eb5026.iso.bz2
6c: fix 32bit pointer truncation (from patch/6c-sugen-types)
aan: fix structure padding for amd64
cdproto: only include binaries for $objtype, filter temporary files
cwfs: fix mtime for dump yyyy directories
fltfmt: fix format strings
fortunes: He wasn't asking about plan9port.
nusb/kb: fix "Home" key producing "7" with some usb keyboards (import
from sources patch/usb-khome)
add games/geigerstats
add experimental wpa/tkip encryption support and wpa key setup program
aux/wpa
---
-sl
* http://img.stanleylieber.com/src/15060/img/1362856601.jpg
next reply other threads:[~2013-03-09 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 19:26 sl [this message]
2013-03-09 19:26 sl
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=edc12f914fe77f4b89d896346994ec2b@9front.org \
--to=sl@9front.org \
--cc=9front@9front.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).