public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Bartolich <alexander.bartolich@gmx.at>
To: Greg Ferguson <gferg@sgi.com>
Cc: David Lawyer <dave@lafn.org>,
	discuss@en.tldp.org, linux-serial@vger.kernel.org
Subject: Re: Maintainer needed for Serial-Programming-HOWTO
Date: Sun, 30 Mar 2003 01:47:19 +0100 (MET)	[thread overview]
Message-ID: <19036.1048985239@www34.gmx.net> (raw)

Greg Ferguson wrote:
> [...] The CVS request can be easily done. Not a problem on our end.

Well, since nobody stood up and protested I had a first go on the document.

http://tux.bartolich.at/Serial-Programming-HOWTO/
http://tux.bartolich.at/Serial-Programming-HOWTO-03-03-30.tar.gz

Not much changed, but at least the examples compile cleanly now with -Wall.
One of them is incomplete and does not link, and hey, I said nothing of
actually
testing them, but that's why I requested a few weeks time.

What is on schedule, apart from that?

-- 
+++ 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

             reply	other threads:[~2003-03-30  0:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-30  0:47 Alexander Bartolich [this message]
2003-03-30  1:11 ` Maintainer needed for Serial-Programming-HOWTO Gary Frerking
2003-03-30  1:36   ` Alexander Bartolich
2003-03-30  2:24     ` Gary Frerking
  -- 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-27 22:55 David Lawyer
2003-03-28  3:51 ` Gary Frerking
2003-03-28 13:51 ` Alexander Bartolich

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=19036.1048985239@www34.gmx.net \
    --to=alexander.bartolich@gmx.at \
    --cc=dave@lafn.org \
    --cc=discuss@en.tldp.org \
    --cc=gferg@sgi.com \
    --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