From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Bugzilla
Date: 05 Jan 2002 10:35:51 +0100 [thread overview]
Message-ID: <1010223352.1056.4.camel@fry> (raw)
In-Reply-To: <200201051055.29219.ermak@netvision.net.il>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
lör 2002-01-05 klockan 09.55 skrev Dan Armak:
> On Friday 04 January 2002 23:39, you wrote:
> > Ok, bugzilla is functionally setup to accept new bugs. If you are a dev
> > with cvs access, you need to create a new bugzilla user with your
> > gentoo.org email address. Those with gentoo.org email addresses
> > automatically get proper dev priviledges.
> OK, question: to make sure I understand the products/components properly: if a
> problem is with an ebuild (i.e. won't compile) the it's assigned to Ebuilds,
> not KDE/Gnome/whatever. Right?
No, Ebuilds are for commiting ebuilds/patches for ebuilds. It's just a
temporary component, as soon as a developer have looked at them they'll
be moved to the correct other component.
> And: why don't we get a different list of components for each of the 3
> products? And what exactly is product Admin?
If you click on one of the products you get a new list in the
component-field (if not that might be some java-script issue).
The Admin module is for infrastructure issues, such as mailinglists,
webserver, cvs/rsync, ...
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-01-05 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 21:39 [gentoo-dev] Bugzilla Damon M. Conway
2002-01-04 22:47 ` Chad M. Huneycutt
2002-01-05 0:27 ` Mikael Hallendal
2002-01-05 8:55 ` Dan Armak
2002-01-05 9:35 ` Mikael Hallendal [this message]
2002-01-05 9:41 ` Dan Armak
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 12:28 Andrew Cooks
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=1010223352.1056.4.camel@fry \
--to=hallski@gentoo.org \
--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