From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Shideleff <bigbob@shideleff.com>
Cc: sid@sources.redhat.com
Subject: Re: pin-pacer glue component
Date: Fri, 06 Aug 2004 14:17:00 -0000 [thread overview]
Message-ID: <20040806141739.GZ20999@redhat.com> (raw)
In-Reply-To: <200408041418.36369.bigbob@shideleff.com>
Hi -
> This patch adds a pin-pacer to the glue components. I have used this
> successfully in combination with a socket component and netcat to feed test
> data from a file into the simulation at a simulation-realistic rate.
Thank you for this contribution, it is in the repository.
For the future, it would help if the changes include bits
like a ChangeLog entry, and perhaps a test suite smoke test
(so we can tell when/if the code breaks in the future).
- FChE
prev parent reply other threads:[~2004-08-06 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 18:18 Robert Shideleff
2004-08-06 14:17 ` Frank Ch. Eigler [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=20040806141739.GZ20999@redhat.com \
--to=fche@redhat.com \
--cc=bigbob@shideleff.com \
--cc=sid@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).