From: Walter Harms <wharms@bfs.de>
To: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Cc: "bugzilla-daemon@kernel.org" <bugzilla-daemon@kernel.org>
Subject: AW: [Bug 220118] New: Lập tức
Date: Wed, 28 May 2025 08:52:19 +0000 [thread overview]
Message-ID: <3b0a1af1121f498b816715bc4ce04170@bfs.de> (raw)
In-Reply-To: <bug-220118-11311@https.bugzilla.kernel.org/>
Hi,
i was curiousabout that bug and got an Access Denied just reading the page.
Is is possible to get info without having a login ?
full msg here:
"You are not authorized to access bug #220118. To see this bug, you must first log in to an account with the appropriate permissions. "
________________________________________
Von: bugzilla-daemon@kernel.org <bugzilla-daemon@kernel.org>
Gesendet: Mittwoch, 14. Mai 2025 05:15:56
An: linux-man@vger.kernel.org
Betreff: [Bug 220118] New: Lập tức
https://bugzilla.kernel.org/show_bug.cgi?id=220118
Bug ID: 220118
Summary: Lập tức
Product: Documentation
Version: unspecified
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: tracpham2210@gmail.com
Regression: No
Lỗi gì đó
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-05-28 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 3:15 [Bug 220118] New: Lập tức bugzilla-daemon
2025-05-14 3:16 ` [Bug 220118] " bugzilla-daemon
2025-05-14 3:51 ` bugzilla-daemon
2025-05-28 8:52 ` Walter Harms [this message]
2025-05-28 9:55 ` AW: [Bug 220118] New: " Alejandro Colomar
2025-06-05 7:36 ` AW: " Walter Harms
2025-06-05 8:11 ` Alejandro Colomar
2025-06-05 12:56 ` Christopher Hoy Poy
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=3b0a1af1121f498b816715bc4ce04170@bfs.de \
--to=wharms@bfs.de \
--cc=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.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