From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: release testing
Date: Sun, 2 Sep 2018 14:01:20 +0200 [thread overview]
Message-ID: <C61D5B9115629F60AF6CD7757940CA70@felloff.net> (raw)
preparing for a new 9front release:
http://lux.felloff.net/usr/cinap_lenrek/9front/changes.txt
http://lux.felloff.net/usr/cinap_lenrek/9front/9front-6703.d310bf4b5f74.386.iso.gz
inquiering on:
- any changes that we dont want to wait another 4 moths to be on the iso
- any bugs and regressions that you know about
- ART
--
cinap
next reply other threads:[~2018-09-02 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 12:01 cinap_lenrek [this message]
2018-09-02 12:18 ` [9front] " hiro
2018-09-03 8:40 ` my /n/dump is something weird karisawa
2018-09-08 22:24 ` [9front] release testing Stanley Lieber
2018-09-08 23:36 ` Kurt H Maier
2018-09-09 0:11 ` Stanley Lieber
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=C61D5B9115629F60AF6CD7757940CA70@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).