From: Gary Thomas <gary@mlbassoc.com>
To: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: re: Updated VNC server
Date: Wed, 27 Aug 2003 14:13:00 -0000 [thread overview]
Message-ID: <1061993579.18003.1294.camel@hermes> (raw)
re: VNC server from Chris Garry.
I am going to see about applying this to the repository. AFAICT,
he has a copyright assignment which covers all works, so there
should be no problem - right?
Also, what, if any, progress has been made on keeping track of
such patches, who's handling them, etc? We discussed earlier
having some sort of document/form/??? that we could use, so that
we'd know (as well as the punters).
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
next reply other threads:[~2003-08-27 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 14:13 Gary Thomas [this message]
2003-08-27 14:37 ` Jonathan Larmour
2003-08-27 19:39 Andrew Lunn
2003-09-01 15:56 ` Bart Veer
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=1061993579.18003.1294.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-maintainers@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).