From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 34974-done@debbugs.gnu.org
Subject: bug#34974: 27.0.50; Moving article error with duplicate suppression disabled
Date: Wed, 10 Apr 2019 14:40:15 +0100 [thread overview]
Message-ID: <878swi0yio.fsf@tcd.ie> (raw)
In-Reply-To: <87bm20mhvn.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 24 Mar 2019 08:06:36 -0700")
tags 34974 fixed
close 34974
quit
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> "Basil L. Contovounesios" <contovob@tcd.ie> writes:
>
>> Sorry, this is a duplicate of bug#34973, which was reported first and
>> where I've now sent my suggested patch.
>>
>> I was going to merge the two bug reports, but then I read that the
>> debbugs 'merge' command requires reports to be assigned to the same
>> package.
>
> Bah, and I'd sent in the "merge" command moments before. Trying too hard
> to be helpful.
>
>> This report was created by the gnus-bug command, which assigned it to
>> both packages emacs and gnus and version 5.13, whereas the other report
>> was presumably created by report-emacs-bug and assigned to the emacs
>> package, version 27.0.50.
>>
>> So, which package+version combination should Gnus bugs be assigned to?
>> How should these two reports be merged? Does merging keep all parties
>> CCed, or do they have to be CCed anew?
I see that Glenn reassigned bug#34973 to both packages emacs and gnus
before merging these two reports, thanks Glenn!
The suggested fix has been merged[1][2], so I'm closing this report.
[1]: https://debbugs.gnu.org/34973#22
[2]: https://debbugs.gnu.org/34974#22
Thanks,
--
Basil
next prev parent reply other threads:[~2019-04-10 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 14:07 bug#34974: 27.0.50; Moving article error with duplicate suppression disabled Basil L. Contovounesios
2019-03-24 14:59 ` Basil L. Contovounesios
2019-03-24 15:06 ` Eric Abrahamsen
2019-04-10 13:40 ` Basil L. Contovounesios [this message]
2019-03-24 15:05 ` Eric Abrahamsen
2019-03-24 17:08 ` Basil L. Contovounesios
2019-03-24 17:14 ` Eric Abrahamsen
2019-03-25 4:16 ` Basil L. Contovounesios
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=878swi0yio.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=34974-done@debbugs.gnu.org \
--cc=eric@ericabrahamsen.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.