From: Tom Tromey <tromey@redhat.com>
To: ddaniels@magic.fr
Cc: eclipse@sources.redhat.com
Subject: Re: bugzilla at redhat: which and where?
Date: Fri, 15 Aug 2003 02:02:00 -0000 [thread overview]
Message-ID: <87isozit3e.fsf@fleche.redhat.com> (raw)
In-Reply-To: <3F31343A.4000109@magic.fr>
>>>>> "Dennis" == Dennis Daniels <ddaniels@magic.fr> writes:
Dennis> I've found a couple of bugs already esp. in the getting
Dennis> started and help pages (ironic, no?).
Yeah. I spent today debugging the help problem.
Dennis> What's worse, I cannot find the 'correct place' to enter bugs
Dennis> on bugzilla.
Dennis> Could someone please tell me the product and component name,
Dennis> or better yet, include a URL for a search string, for the
Dennis> Eclipse bugs?
The component name is 'eclipse'. I'm not sure what product name you
should use. What product names do you see? If you see Red Hat
Enterprise Linux Beta, that is fine.
Dennis> Note the list of dependancies here
Dennis> http://people.redhat.com/~jhealy/eclipse/
Dennis> is not complete.
What is missing? I'll get John to update the list.
Tom
prev parent reply other threads:[~2003-08-15 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 16:59 Dennis Daniels
2003-08-15 2:02 ` Tom Tromey [this message]
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=87isozit3e.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ddaniels@magic.fr \
--cc=eclipse@sources.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).