From: Olaf Meeuwissen <olaf.meeuwissen@avasys.jp>
To: "McDonald, Ira" <imcdonald@sharplabs.com>
Cc: printing-architecture@lists.freestandards.org
Subject: Re: [Printing-architecture] Required prefixes for symbols in new OP specs
Date: Thu, 08 Feb 2007 08:20:40 +0900 [thread overview]
Message-ID: <87iredblmf.fsf@geek.avasys.jp> (raw)
In-Reply-To: <789E617C880666438EDEE30C2A3E8D100105A5DA@mailsrvnt05.enet.sharplabs.com> (Ira McDonald's message of "Wed, 7 Feb 2007 09:27:42 -0800")
"McDonald, Ira" <imcdonald@sharplabs.com> writes:
> Hi Olaf,
>
> What prefix (if any) are you currently using for PCM
> functions, variables, and constants?
We use "fsgpcm" following the examples that JTAPI set. I'll be
getting back on this in your reply to Yasumasu Toratani.
> There was a strong concensus at the OP Steering Committee
> meeting this Monday that we should NOT use 'fsg' as the
> beginning of the prefix for any specs that are not yet
> formally approved.
I don't mind changing it. It's mostly just pulling everthing through
sed 's/fsg/op/g' as we haven't publicly released any code yet ;-)
> [snip]
--
Olaf Meeuwissen EPSON AVASYS Corporation, SE1
FSF Associate Member #1962 sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2
next prev parent reply other threads:[~2007-02-07 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:27 [Printing-architecture] Required prefixes for symbols in new OP specs McDonald, Ira
2007-02-07 19:51 ` Michael Sweet
2007-02-08 3:01 ` Norm Jacobs
2007-02-08 3:16 ` Michael Sweet
2007-02-07 23:20 ` Olaf Meeuwissen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-07 17:36 McDonald, Ira
2007-02-07 23:43 ` Olaf Meeuwissen
2007-02-08 0:07 ` TORATANI Yasumasa
2007-02-07 17:33 McDonald, Ira
2007-02-06 17:04 McDonald, Ira
2007-02-07 0:59 ` Olaf Meeuwissen
2007-02-07 5:19 ` TORATANI Yasumasa
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=87iredblmf.fsf@geek.avasys.jp \
--to=olaf.meeuwissen@avasys.jp \
--cc=imcdonald@sharplabs.com \
--cc=printing-architecture@lists.freestandards.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.