From: Michael Cummings <mcummings@gentoo.org>
To: "gentoo-dev@gentoo.org" <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] RFB : request for bugs ..... so to speak ;P
Date: Sun, 22 Sep 2002 13:14:26 -0400 [thread overview]
Message-ID: <20020922171426.GA13656@datanode.net> (raw)
In-Reply-To: <20020922190647.08B2.BAIN@reaper.org>
Just so the air is clear here (guilty conscience on my part) - that bug
wasn't "below/beneath" me - I really had no clue on how to proceed. Your
perl's bugging out on you, I'm your man. Your portage is bugging out on
you while dealing with perl...I might be your man...
I know you weren't implying otherwise Henti, just didn't want others
thinking I had "shoveled" something off because I didn't want to do
deal with it.
And thanks again for the help yesterday!
Mike
On Sun, Sep 22, 2002 at 07:06:50PM +0200, Henti Smith wrote:
> Can people that have bugs that they just don't have to time to deal with
> because it's "below" them (nor worth they time to find the problem" let
> me know offlist with bug numbers and I'll get cracking on them
>
next prev parent reply other threads:[~2002-09-22 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 17:06 [gentoo-dev] RFB : request for bugs ..... so to speak ;P Henti Smith
2002-09-22 17:14 ` Michael Cummings [this message]
2002-09-22 18:53 ` Henti Smith
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=20020922171426.GA13656@datanode.net \
--to=mcummings@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=mcummings@datanode.net \
/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