From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: serg.foo@gmail.com, acorallo@gnu.org, dancol@dancol.org,
69952@debbugs.gnu.org
Subject: bug#69952: [PATCH] Support pdumping compiled queries by dumping their source
Date: Sat, 06 Jul 2024 10:24:32 +0300 [thread overview]
Message-ID: <86ikxj56fj.fsf@gnu.org> (raw)
In-Reply-To: <24381030-F360-460E-957A-4CB42EE69F77@gmail.com> (message from Yuan Fu on Tue, 18 Jun 2024 23:25:45 -0700)
> From: Yuan Fu <casouri@gmail.com>
> Date: Tue, 18 Jun 2024 23:25:45 -0700
> Cc: Andrea Corallo <acorallo@gnu.org>,
> serg.foo@gmail.com,
> Daniel Colascione <dancol@dancol.org>,
> 69952@debbugs.gnu.org
>
>
>
> > On Jun 15, 2024, at 12:59 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > Ping! Any progress there?
>
> Unfortunately I haven’t make much progress. I’ll report back when I do. Thanks for the reminder!
Any news with this?
next prev parent reply other threads:[~2024-07-06 7:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 3:27 bug#69952: [PATCH] Support pdumping compiled queries by dumping their source Sergey Vinokurov
2024-03-23 7:08 ` Eli Zaretskii
2024-03-23 12:53 ` Sergey Vinokurov
2024-03-23 13:09 ` Eli Zaretskii
2024-04-13 7:41 ` Eli Zaretskii
2024-04-20 8:08 ` Yuan Fu
2024-04-20 9:32 ` Eli Zaretskii
2024-04-20 22:50 ` Yuan Fu
2024-04-21 4:53 ` Eli Zaretskii
2024-04-21 23:41 ` Yuan Fu
2024-04-22 5:47 ` Eli Zaretskii
2024-04-22 6:04 ` Yuan Fu
2024-04-22 6:18 ` Eli Zaretskii
2024-04-22 6:25 ` Yuan Fu
2024-05-04 9:39 ` Eli Zaretskii
2024-05-04 21:29 ` Yuan Fu
2024-05-18 8:38 ` Eli Zaretskii
2024-05-22 6:36 ` Yuan Fu
2024-05-22 12:55 ` Eli Zaretskii
2024-05-29 16:35 ` Andrea Corallo
2024-06-01 17:07 ` Yuan Fu
2024-06-15 7:59 ` Eli Zaretskii
2024-06-19 6:25 ` Yuan Fu
2024-07-06 7:24 ` Eli Zaretskii [this message]
2024-07-20 9:43 ` Eli Zaretskii
2024-07-20 21:06 ` Yuan Fu
2024-07-21 4:30 ` Eli Zaretskii
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=86ikxj56fj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69952@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=casouri@gmail.com \
--cc=dancol@dancol.org \
--cc=serg.foo@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.
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.