From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-xfs@vger.kernel.org, tytso@mit.edu
Subject: Processed: Re: bugs.debian.org: Filesystem scrubbing gets overhand by using both cron jobs and systemd timers
Date: Sun, 08 Jun 2025 19:57:01 +0000 [thread overview]
Message-ID: <handler.s.C.17494125341791884.transcript@bugs.debian.org> (raw)
In-Reply-To: 20250608194000.GA1041370@mit.edu
Processing commands for control@bugs.debian.org:
> reassign 1107480 src:xfsprogs
Bug #1107480 [src:e2fsprogs,src:xfsprogs] bugs.debian.org: Filesystem scrubbing gets overhand by using both cron jobs and systemd timers
Bug reassigned from package 'src:e2fsprogs,src:xfsprogs' to 'src:xfsprogs'.
Ignoring request to alter found versions of bug #1107480 to the same values previously set
Ignoring request to alter fixed versions of bug #1107480 to the same values previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1107480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107480
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
parent reply other threads:[~2025-06-08 19:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250608194000.GA1041370@mit.edu>]
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=handler.s.C.17494125341791884.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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