From: "Matthew J. Turk" <satai@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>, gentoo-user <gentoo-user@gentoo.org>
Subject: [gentoo-dev] sgml testers needed
Date: 05 Feb 2003 14:23:21 -0600 [thread overview]
Message-ID: <1044476601.15438.23.camel@dhcp101183.res-hall.northwestern.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Hi there! I've changed around the way SGML is stored in /etc/sgml and
its catalogs, and to that extend I was hoping that some of you could
help me test it.
If you would like to test it out, unmask sgml-common-0.6.3-r4 in
profiles/package.mask, and upgrade sgml-common. After that, continue
about your business as usual - in particular, try emerging packages that
require SGML documentation (libusb for one, just about any GNOME
package, etc...) or try it out yourself.
If it works, drop me a line. If it doesn't, fill out a bug on
bugs.gentoo.org. If you need to get back to where you were, just
re-mask sgml-common-0.6.3-r4 and follow the steps at
http://www.gentoo.org/~satai/sgmlfix.html and you should be all set.
Thanks!
mjt
--
Matthew J. Turk <satai@gentoo.org>
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-02-05 20:29 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=1044476601.15438.23.camel@dhcp101183.res-hall.northwestern.edu \
--to=satai@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-user@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox