From: Alexander Bartolich <alexander.bartolich@gmx.at>
To: David Lawyer <dave@lafn.org>
Cc: linux-serial@vger.kernel.org, discuss@en.tldp.org
Subject: Re: Maintainer needed for Serial-Programming-HOWTO
Date: Fri, 28 Mar 2003 14:51:03 +0100 (MET) [thread overview]
Message-ID: <3903.1048859463@www31.gmx.net> (raw)
In-Reply-To: 20030327225519.GC1233@lafn.org
David Lawyer:
> [...] So it needs a new maintainer who will rework it and combine the
> two versions (the 1997 and Vern's 1999 which are very much different)
> or just redo the whole thing from scratch. Any volunteers?
I had a look on the version shown on en.tldp.org.
Looks nice and cosy.
However, I never saw the new 1999-stuff from Vern.
And and on the few occasions I toyed with serial programming I read
http://www.easysw.com/~mike/serial, not the HOWTO.
> [...] He actually wrote it in Linuxdoc Format but didn't like
> the rendering the "code" environment, etc. Statements on the
> discussion list about the need to use DocBook and cvs turned him off.
Not sure whether you are searching a programmer or SGML maintainer.
I am a regular user of minicom, but never seriously fed anything than
a socket to select(2).
I feel confident to solve DocBook issues, though.
There are two things I don't like about Serial-Programming-HOWTO.sgml
on http://cvsview.tldp.org/
1. It is a single file.
I prefer separate sect1 referenced as system entities.
But then the whole thing is just 837 lines, real cosy ...
2. The code examples are written inline with <screen>
This is madness. It it absolutely required to make that
<programlisting><inlinemediaobject><imageobject><imagedata
format="linespecific"
fileref="example.c"
/></imageobject></inlinemediaobject></programlisting
and perhaps wrap a Makefile around that to actually compile and
test example.c.
Well, I'd do it if I get a separate directory in CVS.
And if you give me a few weeks time.
And if nobody with more programming experience claims it.
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-03-28 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 22:55 Maintainer needed for Serial-Programming-HOWTO David Lawyer
2003-03-28 3:51 ` Gary Frerking
2003-03-28 13:51 ` Alexander Bartolich [this message]
2003-03-28 15:31 ` Greg Ferguson
-- strict thread matches above, loose matches on Subject: below --
2003-03-28 23:00 Gary Frerking
2003-03-29 21:53 ` David Lawyer
2003-03-30 0:02 ` Gary Frerking
2003-03-30 0:47 Alexander Bartolich
2003-03-30 1:11 ` Gary Frerking
2003-03-30 1:36 ` Alexander Bartolich
2003-03-30 2:24 ` Gary Frerking
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=3903.1048859463@www31.gmx.net \
--to=alexander.bartolich@gmx.at \
--cc=dave@lafn.org \
--cc=discuss@en.tldp.org \
--cc=linux-serial@vger.kernel.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