From: lloda <lloda@sarc.name>
To: 42574-done@debbugs.gnu.org
Cc: pratheblackdiamond@gmail.com
Subject: bug#42574: Probable (system vm trace) bug
Date: Fri, 21 May 2021 20:38:33 +0200 [thread overview]
Message-ID: <FDEDE69F-02D0-4C74-B389-A8C8D7822D5C@sarc.name> (raw)
In-Reply-To: <CAFw+=j0kzmAQpHLKSm9vuShvK9TMmSaGtZsTqK+Ui-FGUFj8=Q@mail.gmail.com>
This has been fixed in f9f55b9ce74898d1b0a77dcc9b4aa260e5cd208d. Apologies for not noticing the earlier patch... there were a couple later duplicates.
Thanks!
prev parent reply other threads:[~2021-05-21 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:38 bug#42574: Probable (system vm trace) bug Prafulla Giri
2020-07-29 15:04 ` bug#42574: Permanent Records Prafulla Giri
2020-08-01 13:05 ` bug#42574: Probable (system vm trace) bug Prafulla Giri
2021-05-21 18:38 ` lloda [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FDEDE69F-02D0-4C74-B389-A8C8D7822D5C@sarc.name \
--to=lloda@sarc.name \
--cc=42574-done@debbugs.gnu.org \
--cc=pratheblackdiamond@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).