From: sl@9front.org
To: 9front@googlegroups.com
Subject: Re: mothra ignores <br>, funky text entry
Date: Sat, 7 Jul 2012 13:10:07 -0500 [thread overview]
Message-ID: <104bd0e4f886033f839698ee77d352f8@sp.inri.net> (raw)
In-Reply-To: <9968e5a44f433829afcaad8fb2445672@sp.inri.net>
> Most likely the slackers in question simply don't know what to do,
> and so they do nothing.
That's not precisely true. Some of the submit bug reports.
-sl
next prev parent reply other threads:[~2012-07-07 18:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 1:31 Ethan Grammatikidis
2012-07-07 1:36 ` sl
2012-07-07 11:12 ` Ethan Grammatikidis
2012-07-07 13:13 ` cinap_lenrek
2012-07-07 16:03 ` Ethan Grammatikidis
2012-07-07 18:08 ` sl
2012-07-08 4:15 ` Ethan Grammatikidis
2012-07-07 12:22 ` cinap_lenrek
2012-07-07 13:39 ` cinap_lenrek
2012-07-07 15:46 ` Ethan Grammatikidis
2012-07-07 17:11 ` cinap_lenrek
2012-07-07 18:09 ` sl
2012-07-07 18:10 ` sl [this message]
2012-07-07 23:31 ` Ethan Grammatikidis
2012-07-08 0:07 ` cinap_lenrek
2012-07-08 5:34 ` Ethan Grammatikidis
2012-07-08 21:00 ` Matthew Veety
2012-07-09 4:16 ` Ethan Grammatikidis
2012-07-09 15:01 ` Julius Schmidt
2012-07-07 17:31 ` cinap_lenrek
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=104bd0e4f886033f839698ee77d352f8@sp.inri.net \
--to=sl@9front.org \
--cc=9front@googlegroups.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;
as well as URLs for NNTP newsgroup(s).