From: Rical Jasan <ricaljasan@pacific.net>
To: Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Bugzilla: editbugs privs
Date: Thu, 22 Feb 2018 06:11:40 -0800 [thread overview]
Message-ID: <6fdd3e6f-0048-bf32-0709-1a98db5e59e1@pacific.net> (raw)
In-Reply-To: <10cb95f5-fb45-3786-4a9d-801b89fcdebd@redhat.com>
On 02/22/2018 05:50 AM, Florian Weimer wrote:
> On 02/22/2018 02:48 PM, Rical Jasan wrote:
>> On 02/22/2018 04:14 AM, Florian Weimer wrote:
>>> On 02/22/2018 10:13 AM, Carlos O'Donell wrote:
>>>> On 02/19/2018 05:42 PM, Rical Jasan wrote:
>>>>> On 02/19/2018 03:04 AM, Florian Weimer wrote:
>>>>>> On 02/19/2018 11:22 AM, Rical Jasan wrote:
>>>>>>> May I be added to the editbugs group in Bugzilla? [0] I'm trying to
>>>>>>> close BZ #6889, but it doesn't look like there is very much I can
>>>>>>> do.
>>>>>>
>>>>>> Please check. I think I have updated your account.
>>>>>
>>>>> That did the trick, thanks!
>>>>>
>>>>> OOC, is there anything in particular I should be saying in a closing
>>>>> comment? It feels weird to just write, "Fixed." I get not wanting
>>>>> empty comments, but I guess there's no (visibly) tracking changes of
>>>>> state otherwise?
>>>>
>>>> Often we say "Fixed in X.Y" as a simple way of making it doubly
>>>> clear when it was fixed and to remind oneself to set the milestone :-)
>>>
>>> Sure, but I think the real reason is that Bugzilla requires something in
>>> that field. Maybe we should just ask for a configuration change to drop
>>> that requirement?
>>
>> Is there otherwise a visible history of the status changes, though?
>> Nice behaviour IMO would be if it auto-generated a "Marked as RESOLVED
>> FIXED by Some Dev." comment if the status changed but the comment was
>> empty, but if you couldn't follow status changes because no comment was
>> generated, that'd be worse than the current situation, which after I
>> thought about it for a bit is why I asked what I should say instead of
>> why I have to write something. :)
>
> Like other Bugzillas, there is a History page for each bug, linked from
> the top right corner. It shows a complete history, except for the
...my visual filter is set to ignore things like "History" hyperlinks
when I'm looking for a record of changes to a webpage.
RESOLVED FIXED ;)
> aspects which have not changed since the filing of the bug (which can be
> confusing). But this does not apply here.
Then yes, it would be convenient to not have to make a comment, though
it is a small inconvenience, and does provide a certain sense of closure
for casual readers of a bug.
Thanks,
Rical
prev parent reply other threads:[~2018-02-22 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 10:22 Bugzilla: editbugs privs Rical Jasan
2018-02-19 11:04 ` Florian Weimer
2018-02-20 1:42 ` Rical Jasan
2018-02-22 9:13 ` Carlos O'Donell
2018-02-22 12:14 ` Florian Weimer
2018-02-22 13:48 ` Rical Jasan
2018-02-22 13:50 ` Florian Weimer
2018-02-22 14:11 ` Rical Jasan [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fdd3e6f-0048-bf32-0709-1a98db5e59e1@pacific.net \
--to=ricaljasan@pacific.net \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).