From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: mricon@gmail.com, mricon@kernel.org, bugs@lists.linux.dev
Subject: Re: Test bug for flag setting
Date: Thu, 30 Mar 2023 20:58:35 +0000 (UTC) [thread overview]
Message-ID: <20230330-b217274c5-dbef58101a2c@bugzilla.kernel.org> (raw)
In-Reply-To: <20230330-niece-fled-173b602dd253@meerkat>
mricon@kernel.org writes via Kernel.org Bugzilla:
(In reply to Bugbot from comment #4)
> This comment was added via replying to the conversation.
> Bugbot should find it.
It did. Now I'm replying inside the bugzilla.
-K
View: https://bugzilla.kernel.org/show_bug.cgi?id=217274#c5
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next prev parent reply other threads:[~2023-03-30 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 18:57 Test bug for flag setting Kernel.org Bugbot
2023-03-30 18:57 ` Kernel.org Bugbot
2023-03-30 19:55 ` Kernel.org Bugbot
2023-03-30 19:56 ` Konstantin Ryabitsev
2023-03-30 20:58 ` Kernel.org Bugbot [this message]
2023-03-30 20:52 ` Kernel.org Bugbot
2023-03-31 17:45 ` Kernel.org Bugbot
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=20230330-b217274c5-dbef58101a2c@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=mricon@gmail.com \
--cc=mricon@kernel.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 NNTP newsgroup(s).