From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Bugs that have been resolved?
Date: Sat, 08 Jun 2002 18:49:49 +0300 [thread overview]
Message-ID: <200206081849.50649.danarmak@gentoo.org> (raw)
In-Reply-To: <20020608161747.GA5636@chello.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9AieeUI2RQ41fiVERAqEsAJ9rircGqb1lXOYRHPGP4Fr/OKfojgCdHgu4
9vrwOWmjkVMJvZL9cjZf5xk=
=aN3x
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-06-08 16:45 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 [this message]
2002-06-09 19:04 ` Magnus Therning
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=200206081849.50649.danarmak@gentoo.org \
--to=danarmak@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