From: Andrew Pinski <pinskia@gmail.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Pieter-Jan Briers <pieterjan.briers@gmail.com>
Subject: Re: Bugzilla mixing up bugs when posting?
Date: Thu, 3 Mar 2022 15:32:06 -0800 [thread overview]
Message-ID: <CA+=Sn1mixFtdzCGj0dNCcSb6zgjKPB8VvF2FcMR0ytNVfNfuMg@mail.gmail.com> (raw)
In-Reply-To: <e91b20c2-4044-264d-b595-88369f6481b0@gmail.com>
On Thu, Mar 3, 2022 at 3:24 PM Pieter-Jan Briers via Overseers
<overseers@sourceware.org> wrote:
>
> 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?
It might be because you did a search and the (site) default is to go
to the next bug in the search.
You can change it via preferences:
After changing a bug: Show the updated bug
Thanks,
Andrew Pinski
>
prev parent reply other threads:[~2022-03-03 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 23:24 Pieter-Jan Briers
2022-03-03 23:32 ` Andrew Pinski [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+=Sn1mixFtdzCGj0dNCcSb6zgjKPB8VvF2FcMR0ytNVfNfuMg@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=overseers@sourceware.org \
--cc=pieterjan.briers@gmail.com \
/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).