From: Jim Kingdon <kingdon@redhat.com>
To: paulb@redhat.com
Cc: elix@sourceware.cygnus.com, lsb-spec@lists.linuxbase.org
Subject: Re: Cooperation between EL/IX and LSB
Date: Sat, 29 Jan 2000 20:36:00 -0000 [thread overview]
Message-ID: <200001300436.XAA12963@devserv.devel.redhat.com> (raw)
In-Reply-To: <00fe01bf6a9c$9be3c020$f8f3fea9@cerberus>
> Ok, we will take a look and see how this might work. The EL/IX std
> has more complexity with regard to options, but should be able to
> find ways of handling this.
OK, the README.SQL file which is in CVS (see
http://www.linuxbase.org/spec/sourceforge.html ) should help explain
what is going on.
Furthermore, I now have built the spec and pretty much understand how
the build process works (which is more than I could have said a day
ago :-)). Stuart had been doing it and it just recently got into CVS,
and it took me a while to get around to getting going with it.
So, yes, ask if you have questions.
next prev parent reply other threads:[~2000-01-29 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-27 10:48 Jim Kingdon
2000-01-29 13:07 ` Paul Beskeen
2000-01-29 20:36 ` Jim Kingdon [this message]
2000-01-30 8:20 ` Stuart Anderson
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=200001300436.XAA12963@devserv.devel.redhat.com \
--to=kingdon@redhat.com \
--cc=elix@sourceware.cygnus.com \
--cc=lsb-spec@lists.linuxbase.org \
--cc=paulb@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).