From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 218693] different UI shows different free disk space
Date: Sun, 07 Apr 2024 23:53:18 +0000 [thread overview]
Message-ID: <bug-218693-13602-ZsmguYXLWp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218693-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218693
Christian Kujau (kernel@nerdbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kernel@nerdbynature.de
--- Comment #1 from Christian Kujau (kernel@nerdbynature.de) ---
Please report this to your distributions or even to the upstream bug trackers
of the applications used, and follow their bug reporting rules. Before doing
that, please consult the documentation of each of these tools how they might
report free space.
--
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:[~2024-04-07 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 21:14 [Bug 218693] New: different UI shows different free disk space bugzilla-daemon
2024-04-07 23:53 ` bugzilla-daemon [this message]
2024-04-08 9:09 ` [Bug 218693] " bugzilla-daemon
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=bug-218693-13602-ZsmguYXLWp@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).