public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Pieter-Jan Briers <pieterjan.briers@gmail.com>
To: overseers@sourceware.org
Subject: Bugzilla mixing up bugs when posting?
Date: Fri, 4 Mar 2022 00:24:50 +0100	[thread overview]
Message-ID: <e91b20c2-4044-264d-b595-88369f6481b0@gmail.com> (raw)

Sorry to send an email again so soon but, is it possible that Bugzilla 
is screwing up and mixing up issue redirects or something?

I went to post a reply and attach a core dump to my issue 
(https://sourceware.org/bugzilla/show_bug.cgi?id=28937), but then 
managed to find that somehow the file got attached to 
https://sourceware.org/bugzilla/show_bug.cgi?id=27695 instead.

So then I go to write a comment explaining that I misplaced the file 
(after checking browser history and feeling severely self-gaslit), and 
then after posting the comment on the second issue it *redirects me back 
to mine!*

Am I going insane because it's midnight and I might be tired or is there 
actually something broken here?


             reply	other threads:[~2022-03-03 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 23:24 Pieter-Jan Briers [this message]
2022-03-03 23:32 ` Andrew Pinski

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=e91b20c2-4044-264d-b595-88369f6481b0@gmail.com \
    --to=pieterjan.briers@gmail.com \
    --cc=overseers@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).