From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56469-done@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#56469: 29.0.50; Unibyte dir in directory_files_internal
Date: Wed, 07 Sep 2022 16:32:17 +0300 [thread overview]
Message-ID: <83v8pzgvj2.fsf@gnu.org> (raw)
In-Reply-To: <87o7vtzkxr.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 05 Sep 2022 21:21:36 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 56469@debbugs.gnu.org
> Date: Mon, 05 Sep 2022 21:21:36 +0200
>
> Skimming this bug report lightly, it seems like the proposed patch was
> applied, but then the discussion continued. It's not clear to me
> whether there's more to be done here -- should this report be closed?
Yes, I think so. Done.
prev parent reply other threads:[~2022-09-07 13:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 17:44 bug#56469: 29.0.50; Unibyte dir in directory_files_internal Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-09 18:17 ` Eli Zaretskii
2022-07-09 18:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-09 18:53 ` Eli Zaretskii
2022-07-10 14:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-10 14:32 ` Eli Zaretskii
2022-07-10 14:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-10 15:07 ` Eli Zaretskii
2022-07-10 15:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-10 15:41 ` Eli Zaretskii
2022-07-10 22:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-11 2:27 ` Eli Zaretskii
2022-09-05 19:21 ` Lars Ingebrigtsen
2022-09-07 13:32 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v8pzgvj2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56469-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.