From: "O'Leary, John W" <john.w.oleary@intel.com>
To: "caml-list@yquem.inria.fr" <caml-list@yquem.inria.fr>
Subject: CFP: Hardware Design and Functional Languages (HFL 2009)
Date: Tue, 18 Nov 2008 08:05:15 -0800 [thread overview]
Message-ID: <4158487B9DEE0647BA23911D1C2279573B6F6A6B@orsmsx501.amr.corp.intel.com> (raw)
Dear Colleagues,
Just a reminder that submissions for HFL 2009 are due this Friday 21
November. Below is a link to the official call. We are looking forward
to another exciting workshop in 2009. We hope you will submit an
abstract and attend the workshop. Please email your submission to
hfl09@hflworkshop.org.
Regards,
Andy Martin (IBM, andy@martin-robson.com)
John O'Leary (Intel, john.w.oleary@intel.com)
IMPORTANT DATES
One-page abstract due: 21 November 2008
Author Notification: 22 December 2008
Final version for proceedings: 2 February 2009
HFL 2009 WORKSHOP: 28-29 March 2009 (York, UK)
FOR MORE INFORMATION
Workshop Website: http://www.hflworkshop.org/hfl09
Call for Abstracts http://www.hflworkshop.org/hfl09/HFL09_CFP.pdf
reply other threads:[~2008-11-18 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4158487B9DEE0647BA23911D1C2279573B6F6A6B@orsmsx501.amr.corp.intel.com \
--to=john.w.oleary@intel.com \
--cc=caml-list@yquem.inria.fr \
/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).