I just tried to alter a bug report thread with no [BUG] in subject into
a proper bug report and immediately confirm the bug at the same time.

However, apparently it is not possible.
https://list.orgmode.org/orgmode/87lemhgwn7.fsf@localhost/ has
"Confirmed." in email body. Yet, the bug status in
https://tracker.orgmode.org/ is "Unacked".

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Ihor Radchenko <yantar92@posteo.net> writes:

> I just tried to alter a bug report thread with no [BUG] in subject into
> a proper bug report and immediately confirm the bug at the same time.
>
> However, apparently it is not possible.
> https://list.orgmode.org/orgmode/87lemhgwn7.fsf@localhost/ has
> "Confirmed." in email body. Yet, the bug status in
> https://tracker.orgmode.org/ is "Unacked".

Altering the subject is a hack and should only be done by maintainers
when they need to declare a report *privately* to to the Woof! inbox.

Here, you didn't used the hack: you declared a new bug.

By design, declaring a bug and updating (confirming, etc.) it need to
be done in separate emails.

This raises one question though: should we let Woof! maintainers have
more power and be able to send already-confirmed bugs?

-- 
 Bastien

Bastien <bzg@gnu.org> writes:

> Altering the subject is a hack and should only be done by maintainers
> when they need to declare a report *privately* to to the Woof! inbox.

Needed a hack for a common use case is awkward.

> This raises one question though: should we let Woof! maintainers have
> more power and be able to send already-confirmed bugs?

Sorry, I do not follow. Could you elaborate?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Ihor Radchenko <yantar92@posteo.net> writes:

>> This raises one question though: should we let Woof! maintainers have
>> more power and be able to send already-confirmed bugs?
>
> Sorry, I do not follow. Could you elaborate?

For now, confirming a bug requires two steps: one to declare the bug
(adding [BUG] in the subject) and another one to mark the bug as
confirmed in a reply to the bug report.

Now consider this email:

  From: user
  Subject: [BUG] My bug report
  
  Confirmed, this is a bug.

If we allow anyone sending such email to declare a bug *and* mark it
confirmed in a single mail (in a single step), then users might be
tempted to abuse this to attract the attention of maintainers.

But maintainers could be allowed this.

If so, your original use-case would be properly handled: on a bug
report where someone forgot to add [BUG] in the subject, you would
add it yourself and and be able to add "Confirmed" in the body.

Does that make sense?

-- 
 Bastien

Bastien <bzg@gnu.org> writes:

> But maintainers could be allowed this.
>
> If so, your original use-case would be properly handled: on a bug
> report where someone forgot to add [BUG] in the subject, you would
> add it yourself and and be able to add "Confirmed" in the body.
>
> Does that make sense?

Yes, it makes sense.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>