public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Magnus Therning <magnus.therning@wanadoo.nl>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Bugs that have been resolved?
Date: Sun, 9 Jun 2002 21:04:16 +0200	[thread overview]
Message-ID: <20020609190416.GE3814@chello.nl> (raw)
In-Reply-To: <200206081849.50649.danarmak@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

Martin Schlemmer (azarah@gentoo.org) beat me to it :-)

Geez, you guys are fast!

/M

On Sat, Jun 08, 2002 at 06:49:49PM +0300, Dan Armak wrote:
> On Saturday 08 June 2002 19:17, Magnus Therning wrote:
> > What does one do in this situation?
> > If one stumbles across a bug that seems to be resolved, but one isn't
> > trusted to mark bugs as resolved in bugzilla.
> 
> Add a comment to the bug saying that it's resolved etc. and wait for the 
> asignee to close it. It will happen eventually, and open bugs for resolved 
> problems aren't very problematic if their comments say that the problem is at 
> least "apparently" resolved.
> 
> >
> > I am referring to bugzilla bug 2100.
> >
> > /M
> 
> -- 
> Dan Armak
> Gentoo Linux developer (KDE)
> Matan, Israel
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> 

-- 
Magnus Therning                    (OpenPGP: 0x6A83A7DF)
magnus.therning@wanadoo.nl
http://www.lysator.liu.se/~magus/

Don't comment bad code - rewrite it.
            - The Elements of Programming Style (Kernighan & Plaugher)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2002-06-09 19:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-08 16:17 [gentoo-dev] Bugs that have been resolved? Magnus Therning
2002-06-08 15:49 ` Dan Armak
2002-06-09 19:04   ` Magnus Therning [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=20020609190416.GE3814@chello.nl \
    --to=magnus.therning@wanadoo.nl \
    --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