From: Gary Thomas <gary@mlbassoc.com>
To: Rutger Hofman <rutger@cs.vu.nl>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] vfnprintf has long long, but fscanf hasn't
Date: Wed, 30 May 2007 15:35:00 -0000 [thread overview]
Message-ID: <465D78B7.9080207@mlbassoc.com> (raw)
In-Reply-To: <465D76C3.8090508@cs.vu.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rutger Hofman wrote:
> Hi list & gurus,
>
> in my checkout of eCos CVS (from ca. Feb. 2007) there is support for the
> long long datatype in vfnprintf, but not in fscanf.
>
> Is it OK if I add long long support to fscanf, and submit a patch? It
> will be best if I add stroll and stroull, too, then.
By all means; that's what community projects are all about.
Feel free to send patches to ecos-patches@ecos.sourceware.org
Don't forget that [most likely] a Copyright assignment will
be required: http://ecos.sourceware.org/assign.html
- --
- ------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGXXi2maKbSsQGV8ARAqquAJ9QLtFStg9Nftc5S2fFvZTBHftDCACfXOHY
iWqcijF+IOs4w7cvFMUOlPY=
=fQSy
-----END PGP SIGNATURE-----
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-05-30 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 13:14 Rutger Hofman
2007-05-30 15:35 ` Gary Thomas [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=465D78B7.9080207@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=rutger@cs.vu.nl \
/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).