From: Stuart Herbert <stuart@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Minor bugzilla annoyance
Date: Mon, 7 Mar 2005 22:40:29 +0000 [thread overview]
Message-ID: <200503072240.29339.stuart@gentoo.org> (raw)
In-Reply-To: <20050307222153.GB23754@kfk4ever.com>
On Monday 07 March 2005 22:21, Maurice van der Pot wrote:
> I'm talking about the way bugzilla is set up: you can't change bugs from
> for instance RESOLVED/TEST-REQUEST to RESOLVED/FIXED in one step. You'd
> have to go through reopening the bug.
Are you sure? It certainly used to be possible to do this.
Best regards,
Stu
--
Stuart Herbert stuart@gentoo.org
Gentoo Developer http://www.gentoo.org/
http://stu.gnqs.org/diary/
GnuPG key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C
--
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-07 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 22:21 [gentoo-dev] Minor bugzilla annoyance Maurice van der Pot
2005-03-07 22:40 ` Stuart Herbert [this message]
2005-03-08 17:21 ` Maurice van der Pot
2005-03-07 22:44 ` Fernando J. Pereda
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=200503072240.29339.stuart@gentoo.org \
--to=stuart@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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