unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>,
	Rical Jasan <ricaljasan@pacific.net>,
	libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Bugzilla: editbugs privs
Date: Thu, 22 Feb 2018 13:14:12 +0100	[thread overview]
Message-ID: <76b984d5-711e-e064-6453-abcb102b1023@redhat.com> (raw)
In-Reply-To: <95ac8c98-2ca2-50d3-4e36-06e5cc3499e9@redhat.com>

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?

Thanks,
Florian


  reply	other threads:[~2018-02-22 12:12 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 [this message]
2018-02-22 13:48         ` Rical Jasan
2018-02-22 13:50           ` Florian Weimer
2018-02-22 14:11             ` Rical Jasan

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=76b984d5-711e-e064-6453-abcb102b1023@redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=ricaljasan@pacific.net \
    /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).