From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Bugzilla upgrade
Date: Wed, 12 Nov 2003 09:54:51 -0500 [thread overview]
Message-ID: <200311120955.12122.vapier@gentoo.org> (raw)
In-Reply-To: <1068645080.32406.6.camel@gentoo.pendulus.net>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 300 bytes --]
On Wednesday 12 November 2003 08:51, Benjamin Coles wrote:
> I also added a
> new resolution status "NOTOURBUG" to make things more organized instead
> of "WONTFIX" which has other characteristics.
wouldnt it be better to use 'UPSTREAM' ?
not our bug seems to convey the wrong connotation ...
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2003-11-12 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 13:51 [gentoo-dev] Bugzilla upgrade Benjamin Coles
2003-11-12 14:54 ` Mike Frysinger [this message]
2003-11-13 0:53 ` Benjamin Coles
2003-11-13 3:30 ` Mike Frysinger
2003-11-12 17:00 ` AW: " Martin Holzer
2003-11-12 19:58 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2003-11-12 20:28 ` [gentoo-dev] " Lisa Seelye
2003-11-13 16:24 ` Jason Stubbs
-- strict thread matches above, loose matches on Subject: below --
2002-12-30 6:39 [gentoo-dev] Bugzilla Upgrade John P. Davis
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=200311120955.12122.vapier@gentoo.org \
--to=vapier@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