From: Eli Zaretskii <eliz@gnu.org>
To: dick <dick.r.chiang@gmail.com>
Cc: 54359@debbugs.gnu.org
Subject: bug#54359: 29.0.50; [PATCH] Undo breaking change to project interface
Date: Sun, 13 Mar 2022 07:48:11 +0200 [thread overview]
Message-ID: <8335jmmmhw.fsf@gnu.org> (raw)
In-Reply-To: <87k0cyu9km.fsf@dick> (message from dick on Sat, 12 Mar 2022 16:47:53 -0500)
> From: dick <dick.r.chiang@gmail.com>
> Date: Sat, 12 Mar 2022 16:47:53 -0500
>
> >From 793d1311b28701931a9343e5196adce82da7833d Mon Sep 17 00:00:00 2001
> From: dickmao <dick.r.chiang@gmail.com>
> Date: Sat, 12 Mar 2022 16:39:28 -0500
> Subject: [PATCH] Avoid breaking the world's `project-current` calls
>
> mitigate 86969f9.
>
> * lisp/progmodes/project.el (cl-generic, cl-lib):
> Rectify the requires
> (project-try-vc): Cache the backend outside project "struct."
> (project-root): Cache the backend outside project "struct."
> (project-files): Cache the backend outside project "struct."
> (project-ignores): Cache the backend outside project "struct."
> * test/lisp/progmodes/project-tests.el
> (project-sparing-backend-discovery): Test it.
Please provide the rationale for this changeset. In particular, what
did the offending commit break, how to reproduce the breakage, and why
the best solution is to revert that commit?
next prev parent reply other threads:[~2022-03-13 5:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 21:47 bug#54359: 29.0.50; [PATCH] Undo breaking change to project interface dick
2022-03-13 5:48 ` Eli Zaretskii [this message]
2022-03-14 19:35 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-17 11:28 ` Lars Ingebrigtsen
2022-03-18 0:56 ` Dmitry Gutov
2022-03-18 9:33 ` Lars Ingebrigtsen
2022-03-18 11:02 ` dick
2022-03-18 11:27 ` Dmitry Gutov
2022-03-18 12:09 ` dick
2022-03-19 18:57 ` Juri Linkov
2022-03-19 14:19 ` Lars Ingebrigtsen
2022-03-19 23:45 ` Dmitry Gutov
2022-03-14 10:38 ` Lars Ingebrigtsen
2022-03-18 0:58 ` Dmitry Gutov
2022-03-18 1:13 ` dick
2022-03-18 11:25 ` 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=8335jmmmhw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54359@debbugs.gnu.org \
--cc=dick.r.chiang@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 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).