From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] usb serial
Date: Thu, 21 Mar 2013 12:31:28 -0400 [thread overview]
Message-ID: <a5cce00e5229b3a1b7ddccb54ba9ca84@ladd.quanstro.net> (raw)
In-Reply-To: <5153B14D-79E4-4882-BE9B-2E3754CE5FE2@gmail.com>
> I have one which I used to write the code and used as my sole console
> to the machine I was debugging for everyday like 3 months. Then I got
> a new one and I stopped using it. Some weeks ago Jeff complained
> about it and Richard and I concurrently found a bug in it. I tested
> it very lightly and it seemed to work. I think that because noone is
> using it daily changes are not tested in it.
>
> Are you using the version from sources? I'll get out my dongle and
> test it again (no pun intended).
thanks for reply! i am using the version from sources.
- erik
prev parent reply other threads:[~2013-03-21 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 14:37 erik quanstrom
2013-03-21 16:04 ` Gorka Guardiola
2013-03-21 16:31 ` 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=a5cce00e5229b3a1b7ddccb54ba9ca84@ladd.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).