From: "Arcady Genkin" <agenkin@thpoon.com>
To: gentoo-dev@gentoo.org
Subject: Re: AW: [gentoo-dev] Gzipped HTML docs in /usr/share/doc
Date: Tue, 19 Feb 2002 23:02:49 -0500 [thread overview]
Message-ID: <87vgcsdcly.fsf@tea.thpoon.com> (raw)
In-Reply-To: <1014164160.1976.1.camel@lipari.mdy.univie.ac.at> (Stefan Boresch's message of "20 Feb 2002 01:16:00 +0100")
Stefan Boresch <stefan@mdy.univie.ac.at> writes:
> I guess I'am expecting (hoping for) some response from
> management. Let me know whether to shut up, swamp bugs.gentoo.org
> or to look into modifying ebuild (the latter may turn out problematic,
> as my programming experience is rather limited...)
I am not the ``management'', but IMO if you could gather the names of
the packages which don't do the right thing with the HTML
documentation into a list, and submit it as one bug, it would,
probably, do. The coding solution to this problem is rather trivial.
Submitting one bug report per package would also be fine, I guess, but
it would take a lot of your time if there are more than a few.
--
Arcady Genkin
Don't read everyting you believe.
next prev parent reply other threads:[~2002-02-20 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 0:16 AW: [gentoo-dev] Gzipped HTML docs in /usr/share/doc Stefan Boresch
2002-02-20 4:02 ` Arcady Genkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 8:04 Stefan Boresch
2002-02-19 8:57 ` AW: " Sebastian Werner
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=87vgcsdcly.fsf@tea.thpoon.com \
--to=agenkin@thpoon.com \
--cc=gentoo-dev@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