From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] more serial questions
Date: Tue, 25 Mar 2014 09:46:42 -0400 [thread overview]
Message-ID: <956bc41b32c2f94c64d3b81cf565d110@brasstown.quanstro.net> (raw)
In-Reply-To: <1D432047-DD58-4730-9386-F242419B88A0@gmail.com>
> I didn't add that, your guess is as good as mine.
ok.
> That it was implemented after and I was short on time. They should.
cool. i wanted to rule out some sort of odd h/w interaction.
- erik
prev parent reply other threads:[~2014-03-25 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 0:12 erik quanstrom
2014-03-25 7:45 ` Gorka Guardiola
2014-03-25 13:46 ` erik quanstrom [this message]
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=956bc41b32c2f94c64d3b81cf565d110@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).