From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
Date: Tue, 17 May 2005 12:58:35 -0400 [thread overview]
Message-ID: <200505171258.35925.mcummings@gentoo.org> (raw)
In-Reply-To: <200505171242.15421.mcummings@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
yeah, i hit send, then jforman hit send. sorry.
On Tuesday 17 May 2005 12:42 pm, Michael Cummings wrote:
> (fearing the jeff wrath)
>
> can we get the dup status added back in though? i know, i know, we're being
> nitpicky, and not too many folks have stood up and applauded this effort
> like they should have (ahem). Just...unsettling to see bugs marked as
> resolved - make it sound like i did something rather than find that the
> same problem had been reported a few times :)
>
> On Tuesday 17 May 2005 11:47 am, Jeffrey Forman wrote:
> > Bingo, I found the correlation between those bugs and the previous ones
> > mentioned by Daniel. They have all been marked as duplicates of other
> > bugs. Therefore bugzilla does not put a "resolution" in there, only
> > marking them as status: resolved.
> >
> > -Jeffrey
> >
> > On Tue, 2005-05-17 at 11:19 -0400, Aaron Walker wrote:
> > > Jeffrey Forman wrote:
> > > > That seems odd, then again, those are VERY old bugs. Way before my
> > > > time of looking at bugzilla to upgrade.
> > >
> > > Don't think it has anything to do with age. Just marked this one a dup
> > > this morning.
> > >
> > > http://bugs.gentoo.org/show_bug.cgi?id=92539
--
-----o()o---------------------------------------------
Michael Cummings | #gentoo-dev, #gentoo-perl
Gentoo Perl Dev | on irc.freenode.net
-----o()o---------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-17 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 0:17 [gentoo-dev] UPGRADE complete bugs.gentoo.org Jeffrey Forman
2005-05-17 0:25 ` Georgi Georgiev
2005-05-17 0:41 ` Jeffrey Forman
2005-05-17 8:31 ` Michael Cummings
2005-05-17 12:46 ` Jonathan Smith
2005-05-17 13:04 ` Alin Dobre
2005-05-17 13:43 ` Georgi Georgiev
2005-05-17 13:54 ` Jonathan Smith
2005-05-17 14:05 ` Alin Dobre
2005-05-17 14:30 ` Jeffrey Forman
2005-05-17 14:37 ` Jonathan Smith
2005-05-17 14:50 ` Daniel Drake
2005-05-17 15:02 ` Jeffrey Forman
2005-05-17 15:19 ` Aaron Walker
2005-05-17 15:47 ` Jeffrey Forman
2005-05-17 16:18 ` Jeffrey Forman
2005-05-17 16:42 ` Michael Cummings
2005-05-17 16:52 ` Jeffrey Forman
2005-05-17 17:36 ` Donnie Berkholz
2005-05-17 18:15 ` Jan Kundrát
2005-05-17 18:28 ` Jeffrey Forman
2005-05-17 16:58 ` Michael Cummings [this message]
2005-05-17 14:13 ` Jonathan Smith
2005-05-17 14:25 ` Jeffrey Forman
2005-05-18 12:22 ` Henrik Brix Andersen
2005-05-20 8:30 ` [gentoo-dev] " R Hill
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=200505171258.35925.mcummings@gentoo.org \
--to=mcummings@gentoo.org \
--cc=gentoo-dev@lists.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