From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] usb/serial control open
Date: Sun, 23 Mar 2014 07:04:11 +0200 [thread overview]
Message-ID: <cbf2ca6e1961097b3a91d01a64e58381@proxima.alt.za> (raw)
In-Reply-To: <20140324004134.673DBB827@mail.bitblocks.com>
> The issue is program A can leave things in non-working order
> and program B running after A has to deal with this. This is
> no different from bringing up a system in a known good state.
I think I'd rather be able to have a preceding program be able to set
up the interface and leave it than cater for possible failures and
needing all serial handling programs, irrespective of their
application, needing to go through the set up motions. I'm with Erik
on this one.
++L
next prev parent reply other threads:[~2014-03-23 5:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 18:09 erik quanstrom
2014-03-23 18:34 ` Gorka Guardiola
2014-03-23 18:55 ` erik quanstrom
2014-03-23 19:47 ` Gorka Guardiola
2014-03-23 19:55 ` Gorka Guardiola
2014-03-23 20:32 ` erik quanstrom
2014-03-23 21:08 ` Gorka Guardiola
2014-03-24 1:49 ` erik quanstrom
2014-03-23 21:32 ` Bakul Shah
2014-03-23 21:53 ` erik quanstrom
2014-03-23 22:02 ` Bakul Shah
2014-03-24 0:32 ` erik quanstrom
2014-03-24 0:41 ` Bakul Shah
2014-03-23 5:04 ` lucio [this message]
2014-03-23 19:53 ` Gorka Guardiola
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=cbf2ca6e1961097b3a91d01a64e58381@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).