From: Spencer Baugh <sbaugh@janestreet.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dmitry Gutov <dmitry@gutov.dev>,
69233@debbugs.gnu.org, 69188@debbugs.gnu.org
Subject: bug#69233: bug#69188: 30.0.50; project-files + project-find-file is slow in large repositories
Date: Fri, 23 Feb 2024 16:34:38 -0500 [thread overview]
Message-ID: <ierh6hy6f0x.fsf_-_@janestreet.com> (raw)
In-Reply-To: <86bk8dr0g1.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 18 Feb 2024 22:18:06 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sun, 18 Feb 2024 22:11:43 +0200
>> Cc: sbaugh@janestreet.com, 69233@debbugs.gnu.org
>> From: Dmitry Gutov <dmitry@gutov.dev>
>>
>> On 18/02/2024 21:45, Eli Zaretskii wrote:
>> >> Date: Sun, 18 Feb 2024 21:42:37 +0200
>> >> Cc:69233@debbugs.gnu.org
>> >> From: Dmitry Gutov<dmitry@gutov.dev>
>> >>
>> >> On 18/02/2024 20:56, Eli Zaretskii wrote:
>> >>> This is a duplicate of another bug report you submitted not long ago.
>> >> Any reason I didn't receive the first one to my inbox?
>> > I don't have the foggiest, sorry.
>>
>> It seems Spencer didn't get the confirmation email either, or he
>> wouldn't resubmit.
>
> One can know if debbugs received a report via the Web interface.
Yes, it seems that all my email was backed up for a day or so, for
whatever reason. Sorry for the noise.
(Or maybe I just think this is such an important bug that I submitted it
twice :) )
next prev parent reply other threads:[~2024-02-23 21:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 22:55 bug#69188: 30.0.50; project-files + project-find-file is slow in large repositories Spencer Baugh
2024-02-18 18:56 ` bug#69233: " Eli Zaretskii
2024-02-18 19:42 ` Dmitry Gutov
2024-02-18 19:45 ` Eli Zaretskii
2024-02-18 20:11 ` Dmitry Gutov
2024-02-18 20:18 ` Eli Zaretskii
2024-02-23 21:34 ` Spencer Baugh [this message]
2024-04-13 2:34 ` bug#69188: " Dmitry Gutov
2024-04-16 23:48 ` Dmitry Gutov
2024-04-29 20:27 ` bug#69188: bug#69233: " Spencer Baugh
2024-05-05 0:29 ` Dmitry Gutov
2024-04-29 21:04 ` Spencer Baugh
2024-05-05 3:32 ` Dmitry Gutov
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ierh6hy6f0x.fsf_-_@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=69188@debbugs.gnu.org \
--cc=69233@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).